Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

redirect in Server Actions & route.push do not work in Intercepting Routes anymore #64535

Closed
K1NXZ opened this issue Apr 16, 2024 · 3 comments · Fixed by #64532
Closed

redirect in Server Actions & route.push do not work in Intercepting Routes anymore #64535

K1NXZ opened this issue Apr 16, 2024 · 3 comments · Fixed by #64532
Labels
bug Issue was opened via the bug report template. locked Navigation Related to Next.js linking (e.g., <Link>) and navigation.

Comments

@K1NXZ
Copy link

K1NXZ commented Apr 16, 2024

Link to the code that reproduces this issue

https://github.com/K1NXZ/nextjs-intercept-redirect

To Reproduce

  1. Start the application with pnpm dev
  2. Navigate to http://localhost:3000
  3. Click a link to open an intercepting route
  4. Submit a form

Current vs. Expected behavior

I expected to get redirected to the root / but nothing happens after submitting a form and performing a server action.

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.4.0: Fri Mar 15 00:10:42 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 10
Binaries:
  Node: 18.18.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.15.6
Relevant Packages:
  next: 14.3.0-canary.4 // Latest available version is detected (14.3.0-canary.4).
  eslint-config-next: 14.3.0-canary.4
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.5
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

App Router, Routing (next/router, next/navigation, next/link)

Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local)

Additional context

I noticed this bug got introduced in 14.2.0 and is still in 14.3.0-canary.4.

@K1NXZ K1NXZ added the bug Issue was opened via the bug report template. label Apr 16, 2024
@github-actions github-actions bot added the Navigation Related to Next.js linking (e.g., <Link>) and navigation. label Apr 16, 2024
@mubashir-zenkoders
Copy link

I am too getting the same issue, programmatical routing is not working inside server actions.

@denexapp
Copy link

common ztanner W

Copy link
Contributor

github-actions bot commented May 2, 2024

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@github-actions github-actions bot added the locked label May 2, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template. locked Navigation Related to Next.js linking (e.g., <Link>) and navigation.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants