You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When usefetch carries the token request interface from cookies, if the returned status code is 401, I called loginInvalid(), but navigateTo did not take effect
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered:
useAsyncData or useFetch functions should not have side effects. They are not guaranteed to run. For example, we support payload extraction and running them at generate time.
You should also not use useFetch in order to perform a request. Instead just use $fetch directly.
Environment
Reproduction
export const BASE_URL = process.env.BASE_URL;
import { getToken, delToken } from "#imports";
const request = () => {
};
export default request();
Describe the bug
When usefetch carries the token request interface from cookies, if the returned status code is 401, I called loginInvalid(), but navigateTo did not take effect
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: