Next.js - Dynamic Route not working in Production Mode when running `Next Build && Next Start`

Can anyone here think of a reason that a dynamic route might work in dev mode but not in production mode when running

next build && next start

? We have a project we are working on that has a dynamic

path

being created in the query to sanity, and we are using a wildcard

[path].tsx

to catch those routes. The query seems to work fine, and in dev we can get to all the pages using this route. But in production we get empty pages for

/page1

, and 404s for

/page1/childpage

This here

[path].tsx

catches only the first level of path like

/page1

and

/page2

. Not the sub path routes!! To catch all of them you have to use this one: https://nextjs.org/docs/routing/dynamic-routes#catch-all-routes

Yeah, I tried that and it seems to fix the 404s. What it doesn't help with is why the pages are rendering empty when in production mode, but working fine in dev mode

In the dev mode 404 pages a not supported

no, sorry... not what i mean.

So, I've changed to the catch-all route

That route, in dev mode, returns a page with content from Sanity as expected

in production mode it returns empty

i think i might have run into this and it was because i had a collision with a static and dynamic page. i had a hard coded page (about.tsx) and then a dynamic route ([slug].tsx) where sanity also has an about slug. not sure if that's related

The hard coded page should always wins as i know 🙂

when i had the collision, i remember the dang kind of bug where it didn't show up when deployed but was fine locally. best to just remove all collisions

learned that the hard way lol

Hmm. There shouldn't be a collision between paths I don't think. Thanks for the input though... this is an odd one

Are you using getStaticProps and getStaticPaths, ? Also, are you deploying on Vercel? If so, your Function Logs might provide some insight.

Deploying on Netlify at the moment, but have the same issue locally. Have managed to use

getStaticProps

and

getStaticPaths

to get things to render properly on first load, but now we have a different issue - when clicking a link to change to another page that uses the same route but has different components, the page is not re-rendering properly, it looks like its only updating the page title

When you’re navigating between pages locally, what shows up in your terminal where you’re running the dev server? Is it similar to this?

Sorry I kind of ghosted there... Got sucked into actually fixing the thing and then had meetings etc. It turns out that the way our guys were serializing the content wasn't refreshing the props when the page changed. So they sorted that and now the rendering updates as it should! Thanks for all the help!

That’s great! I’m happy to hear it. Thanks for the update. 🙂