Intercepting + Dynamic Routes, Jumping the page causes a forced refresh #62207
Labels
bug
Issue was opened via the bug report template.
locked
Parallel & Intercepting Routes
Related to Parallel and/or Intercepting routes.
Comments
|
I have come across a similar issue and found that I can reproduce it locally when using the edge runtime, but with the nodejs runtime it only seems to happen when deployed to Vercel. |
balazsorban44
added
the
Parallel & Intercepting Routes
ztanner
added a commit
that referenced
this issue
Apr 23, 2024
…are (#64923) We currently have logic spread in multiple places that normalize `nxtP` parameters into their regular names, ie `nxtPfoo` -> `foo`. However we don't apply this same logic to `nxtI`, which conceptually is another parameter but for route interception. As a result, the interception route would 404 when deployed because it'd be missing the interception parameter. This moves the normalization check into a util and updates the spots I could find where we handle `nxtP` to also handle `nxtI`. ### Test Plan Added a new test, and validated via these deploys: **Working**: [Link](https://vtest314-e2e-tests-m889gxi4p-vtest314-ijjk-testing.vercel.app/) **Non-Working**: [Link](https://vtest314-e2e-tests-8sa5t9uau-vtest314-ijjk-testing.vercel.app/) Fixes #62207 Closes NEXT-3204
|
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Link to the code that reproduces this issue
https://github.com/bosinc/next-bug
To Reproduce
Page anybuttonCurrent vs. Expected behavior
When accessing dynamic interception routes, the page will be forced to refresh.
Note:
Provide environment information
Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:27 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T8103 Binaries: Node: 18.18.0 npm: 10.1.0 Yarn: 1.22.19 pnpm: 8.15.3 Relevant Packages: next: 14.1.0 eslint-config-next: 14.1.0 react: 18.2.0 react-dom: 18.2.0 typescript: 5.3.3 Next.js Config: output: N/AWhich area(s) are affected? (Select all that apply)
Not sure
Which stage(s) are affected? (Select all that apply)
Vercel (Deployed)
Additional context
No response
The text was updated successfully, but these errors were encountered: