react-admin always remembers users last visited view.

[WiXSL]

You can see this in the demo.
1.- Login
2.- Browse to any view other than the Dashboard.
3.- Log out.
4.- Log in again.

Result: you get redirected to the latest view you visited.
Expected: You should be redirected to the Dashboard.

Changing the Login component doesn't seem to work:

const Login = () => {
    //...
    const login = useLogin();
    const location = useLocation<{ nextPathname: string } | null>();

    const handleSubmit = (auth: FormValues) => {
        setLoading(true);
-       login(auth, location.state ? location.state.nextPathname : '/').catch(
+       login(auth, '/').catch(
            (error: Error) => {
                setLoading(false);
                notify(
                    typeof error === 'string'
                        ? error
                        : typeof error === 'undefined' || !error.message
                        ? 'ra.auth.sign_in_error'
                        : error.message,
                    'warning'
                );
            }
        );
    };
   //...

[WiXSL]

The problem seems to be in the useLogin hook.
It always uses the location state.

const useLogin = (): Login => {
    const authProvider = useAuthProvider();
    const location = useLocation();
    const locationState = location.state as any;
    const history = useHistory();
    const nextPathName = locationState && locationState.nextPathname;

    const login = useCallback(
        (params: any = {}, pathName = defaultAuthParams.afterLoginUrl) =>
            authProvider.login(params).then(ret => {
                // --> nextPathName gets used every time if exists
                history.push(nextPathName || pathName);
                return ret;
            }),
        [authProvider, history, nextPathName]
    );

    const loginWithoutProvider = useCallback(
        (_, __) => {
            history.push(defaultAuthParams.afterLoginUrl);
            return Promise.resolve();
        },
        [history]
    );

    return authProvider ? login : loginWithoutProvider;
};

[fzaninotto]

That's by design: when a user is logged out bu a 403 response from the server and logs in again, they want to go back to the page they were visiting before.

That means we must distinguish between an automated logout caused by a 403 (which should remember the last page) and a manual logout caused by a click on the "Logout" button (which should not remember the last page).