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

Interception of a parallel route clash #58296

Closed
1 task done
JavierMartinz opened this issue Nov 10, 2023 · 3 comments
Closed
1 task done

Interception of a parallel route clash #58296

JavierMartinz opened this issue Nov 10, 2023 · 3 comments
Labels
bug Issue was opened via the bug report template. locked

Comments

@JavierMartinz
Copy link

Link to the code that reproduces this issue

https://github.com/javiermartinz/nextgram

To Reproduce

  1. Visit https://nextgram-javiermartinz.vercel.app
  2. Click on the buggy link
  3. You'll see the app crashing because the route is intercepted.

Current vs. Expected behavior

Current

Dynamic route intercepted, although there is an static route for it

Expected

Only dynamic route intercepted. Static route should use a regular redirect to be fully shown.

Verify canary release

  • I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.0.0: Fri Sep 15 14:41:43 PDT 2023; root:xnu-10002.1.13~1/RELEASE_ARM64_T6000
Binaries:
  Node: 20.8.0
  npm: 10.1.0
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 14.0.3-canary-0
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: N/A
Next.js Config:
  output: N/A

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

App Router

Additional context

No response

@JavierMartinz JavierMartinz added the bug Issue was opened via the bug report template. label Nov 10, 2023
@JavierMartinz

This comment has been minimized.

@JavierMartinz
Copy link
Author

Fixed with #59752

Copy link
Contributor

github-actions bot commented Jan 5, 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 Jan 5, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 5, 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
Projects
None yet
Development

No branches or pull requests

1 participant