Closed ehsanrezaeee closed 1 week ago
Hi @ehsanrezaeee, this is due to action queuing and is expected. The action might return a revalidate payload so the client needs to wait. We recommend using revalidatePath
/redirect
instead of router.push
, which will also save another round trip to the server.
Thanks for explaining the issue.
Link to the code that reproduces this issue
https://github.com/ehsanrezaeee/next-router-report
To Reproduce
Current vs. Expected behavior
i expected to redirect to the specific url but instead the url changed and the redirection didnt happen
Provide environment information
Which area(s) are affected? (Select all that apply)
Navigation
Which stage(s) are affected? (Select all that apply)
next dev (local), next build (local), next start (local), Other (Deployed)
Additional context
i tested the application on the production and still having issues i mentioned. i didnt test on the canary latest version.