Intercepting dynamic parallel routes returns 404 only on staging

PatrykWojcieszak commented 6 months ago

Link to the code that reproduces this issue

repository: https://github.com/PatrykWojcieszak/next-intercepting staging env: https://next-intercepting.vercel.app/

To Reproduce

npm install
npm run dev
click test page
click on any of the links
click on any of the new links
intercepted route: text should be displayed
go to staging env
repeat steps from 3 to 5
404 error will be displayed

Current vs. Expected behavior

I expect the route to be intercepted on staging env as it is intercepted on local env.

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
Binaries:
  Node: 20.10.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.1.3
  eslint-config-next: 14.1.3
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.2
Next.js Config:
  output: N/A

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

App Router

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

Vercel (Deployed)

Additional context

On my local machine it works fine for both development and production builds. I have noticed the following differences inside the url structure when inspecting the network tab: Local machine Next-Url: /test/link4/children/link4/newLink4

Staging Environment Next-Url: /test/%5Bdynamic%5D/children/%5Bdynamic%5D/newLink4

github-actions[bot] commented 4 months ago

We cannot easily recreate the issue with the provided information. Please add a minimal reproduction in order for us to be able to help more efficiently.

Why was this issue marked with the `please simplify reproduction` label?

There was a reproduction provided, but due to its complexity, we cannot easily reproduce the issue.

An ideal minimal reproduction (unless relevant):

is not part of a monorepo
does not require secrets to run
does not reference private registry dependencies
has as few dependencies as possible
excludes unrelated pages/routes
does not require a database/third-party service to run
only includes the code necessary to reproduce the issue
is tested against next@canary to make sure your issue has not already been fixed

In general, assume that we should not go through a lengthy onboarding process at your company code only to be able to verify an issue.

If you cannot create a clean reproduction, another way you can help the maintainers' job is to pinpoint the canary version of next that introduced the issue. Check out our releases, and try to find the first canary release that introduced the issue. This will help us narrow down the scope of the issue, and possibly point to the PR/code change that introduced it. You can install a specific version of next by running npm install next@<version>.

What happens if I don't provide a sufficient minimal reproduction?

Issues with the please simplify reproduction label that receive no meaningful activity (e.g. new comments with a simplified reproduction link) are automatically closed and locked after 30 days.

If your issue has not been resolved in that time and it has been closed/locked, please open a new issue with the required reproduction.

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps.

I think my reproduction is good enough, why aren't you looking into it quicker?

We look into every Next.js issue and constantly monitor open issues for new comments.

However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Providing a minimal reproduction from the start without asking helps us look into issues much more quickly, as we can easily verify if the reported bug is related to Next.js. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.

Useful Resources

PatrykWojcieszak commented 4 months ago

Hi @ztanner I've updated description. I've added new, clean repository and link to staging env of that repository and information about one thing I noticed in the network tab.

ztanner commented 3 months ago

Thanks for updating it! I will take a look.

vercel / next.js