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

ConcurrentFeature not working with dynamic routing #31212

Closed
Alexandredc opened this issue Nov 9, 2021 · 3 comments
Closed

ConcurrentFeature not working with dynamic routing #31212

Alexandredc opened this issue Nov 9, 2021 · 3 comments
Labels
bug Issue was opened via the bug report template.

Comments

@Alexandredc
Copy link

What version of Next.js are you using?

12.0.4-canary.0

What version of Node.js are you using?

16.4.2

What browser are you using?

Chrome

What operating system are you using?

MacOS

How are you deploying your application?

next dev

Describe the Bug

Dynamic routing is not working when concurrentFeatures and serverComponents flag are enabled.

Error : Could not find files for /account/test in .next/build-manifest.json

Screenshot 2021-11-09 at 16 36 01

Expected Behavior

Dynamic routing should work when concurrent mode is enabled.

To Reproduce

Here is a Codesandbox that reproduce the issue :
https://codesandbox.io/s/keen-khayyam-e14cz

Navigate to /account/test

@Alexandredc Alexandredc added the bug Issue was opened via the bug report template. label Nov 9, 2021
@AHBruns
Copy link

AHBruns commented Nov 18, 2021

Experiencing the same issue. What's odd is that is seems the dynamic route is actually being treated as a static route. For instance, I have the following:

Screen Shot 2021-11-17 at 8 40 42 PM

and going to /book/abc gives:

Screen Shot 2021-11-17 at 8 41 20 PM

but going to /book/[id] loads the page.

@huozhi
Copy link
Member

huozhi commented Feb 18, 2022

It's fixed in next.js 12.1.0 now! Please checkout the doc for migration.

@huozhi huozhi closed this as completed Feb 18, 2022
@github-actions
Copy link
Contributor

This closed issue has been automatically locked because it had no new activity for a month. 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 locked as resolved and limited conversation to collaborators Mar 20, 2022
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.
Projects
None yet
Development

No branches or pull requests

5 participants