router.push doesn't work in production

[itzAymvn]

Summary

This function is supposed to redirect the user to the /dashboard route if the sign in is successful, It works like that when npm run dev and everything perfect. But when I run the build (npm run build & npm run start) it just logs both "Before redirect" and "After redirect" but doesn't actually redirect.

async function handleSubmit(event) {
    event.preventDefault();

    // reset message and error
    setMessage(null);
    setError(null);

    // get form data
    const form = event.target;
    const formData = new FormData(form);
    const email = formData.get("email");
    const password = formData.get("password");

    // validate
    if (!email || !password) {
        setError("Please fill in all fields");
        return;
    }

    // when everything is ok, change the content of the button to "Loading..."
    setButtonContent("Loading...");

    // send data to server
    try {
        const data = await signIn("credentials", {
            redirect: false,
            email,
            password,
        });

        if (data.error !== null) {
            setError(data.error);
            setButtonContent("Login");
            return;
        }
    } catch (error) {
        console.log(error);
        return;
    }

    console.log("Before redirect");
    router.push("/dashboard");
    console.log("After redirect");
}

Additional information

No response

Example

No response

[bartekczyz]

Experiencing exactly the same issue

[itzAymvn]

I made a fresh nextjs install and it works just perfect in the production build

[icyJoseph]

Is this using App Router? or Page Dir?

[itzAymvn]

No I didn't fix it, when the user put in correct data, it doesn't redirect them like it does when in dev mode

[icyJoseph]

The API route that handles signin, is that one of the new route.ts handlers?

[itzAymvn]

/api/auth/[...nextauth]/route.js

[itzAymvn]

Here is the repo: https://github.com/itzaymvn/aymvn.tech

[bartekczyz]

@itzAymvn did you have a chance to take a look at the repro repository? :)

[bartekczyz]

@itzAymvn I've created an issue for that: #52122

[bartekczyz]

@itzAymvn I don't know why exactly, but in my case it wouldn't redirect because at the time redirecting, router was not aware of user being successfully authenticated, so I had to refresh the state manually

router.refresh()

and then

router.replace('route-to-redirect')

So in your case it would be

    console.log("Before redirect");
    router.refresh(); // dirty fix, but it works
    router.push("/dashboard");
    console.log("After redirect");

CC @icyJoseph

[saman2007]

A i am using next js pages router, i added await router.prefetch(path, path, {priority: true}) exactly before i call router.push(path) and it worked!

[devMiguelCarrero]

It's working with router.prefetch(). I had the same issue, thank you very much!

[nicolasheady]

Not even router.prefetch() is working for me. Neither does putting a flag inside useEffect. Neither does refresh() before push(), or replace().

[CaioMS2000]

I'm using Next 15.0.3, and I'm having same issue, router.push is triggering a GET request to the target route but not properly redirecting the user to the target route. And router.refresh is not working as well, so I'm using window.location.href = "/your-route" until I fix this.

[jamesopti]

Our issue is that middleware is running that does not get updated cookies that were set by a previous network request prior to calling push.

This has worked for us for 3+ years and suddenly broke.

[xiliumz]

I fixed the issue by removing the router.prefetch('/dashboard') line from my LoginForm component.

I believe the problem occurred because I attempted to prefetch the dashboard page before a user logged in. This caused an issue because I have middleware in place that redirects users to the root / page if they try to access the dashboard without a session cookie.

[Reynalroddy]

This issue is the most annoying ever..this is'nt my first time using next-auth..how tf will a router.push not work even after getting a console.log just before thee router.push...nothing seems to work..might just dump it for a custom auth..what a waste of time.damn

[Reynalroddy]

works on dev build..but for some reason production builds don't work.

[determinedcount]

Dealt with this same issue, the solution was similar to this from @xiliumz, but there was no prefetch(). If an unauth'd user clicked on a button that calls router.push('/edit'), middleware redirected them to /login. Then they would successfully auth and a router.push('/edit') on /login would run, but it did nothing. The solution was to point the original button at /login instead of /edit (middleware redirects already-auth'd users from /login to /edit anyway) and, for good measure, put a router.refresh() in front of /login's router.push().