Getting a 404 page when using the parallel route and catch-all route together. Please help.
Unanswered
Uni Mocha posted this in #help-forum
Uni MochaOP
I'm currently using nextjs 13.5.6 (latest), and I'm using the app route.
I saw on the Parallel routes page of the official documentation that you can use a catch-all route, so I tried to use it.
https://nextjs.org/docs/app/building-your-application/routing/parallel-routes#dismissing-a-modal
Currently, I have defined a Route Group called (default-layout) and defined a layout.tsx in it to render the header and body through a parallel route, so I have configured the directory like image.
When accessing with '/', page.tsx is rendered just below @header, so header is displayed normally.
However, when accessing the '/search/nearby' page, the page.tsx inside [...catchAll] is rendered and the header with the back button is displayed, but a 404 page is displayed.
Please help me if I'm doing something wrong or if there is a bug for this. 😢
I saw on the Parallel routes page of the official documentation that you can use a catch-all route, so I tried to use it.
https://nextjs.org/docs/app/building-your-application/routing/parallel-routes#dismissing-a-modal
Currently, I have defined a Route Group called (default-layout) and defined a layout.tsx in it to render the header and body through a parallel route, so I have configured the directory like image.
When accessing with '/', page.tsx is rendered just below @header, so header is displayed normally.
However, when accessing the '/search/nearby' page, the page.tsx inside [...catchAll] is rendered and the header with the back button is displayed, but a 404 page is displayed.
Please help me if I'm doing something wrong or if there is a bug for this. 😢
1 Reply
Uni MochaOP
plz...