generateStaticParams with dynamicParams false does not show not-found page on production

[smitbarmase]

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 22.5.0: Thu Jun  8 22:22:20 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.17.0
      npm: 9.6.7
      Yarn: N/A
      pnpm: 8.6.9
    Relevant Packages:
      next: 13.4.19
      eslint-config-next: 13.4.18
      react: undefined
      react-dom: undefined
      typescript: 5.1.6
    Next.js Config:
      output: N/A

Which area(s) of Next.js are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue or a replay of the bug

https://github.com/smitbarmase/rapp

To Reproduce

Navigate to http://localhost:3000/blog/4, which is not path in generateStaticParams.

Describe the Bug

On prod, it shows server error in my private repository. On dev, in this repository, it does not render not-found page.

Expected Behavior

It should render closest not-found in tree.

Which browser are you using? (if relevant)

Chrome

How are you deploying your application? (if relevant)

Vercel

[nitinTJ]

facing the similar issue

[yvonnetangsu]

Also facing similar issue. It never shows the not-found page for me.

[ceIia]

funny enough, the opposite is also happening.

when using dynamicParams = true in dev mode, the segments not returned by generateStaticParams will not get generated in dev mode and return a 404. in production, they work fine and get built as expected.

[Ch1keen]

Maybe a similar issue here: #54239

[Simone-cm]

I was getting the same problem but then I just used

export const dynamicParams = false;

on the page.tsx that I needed and the problem was gone.

Maybe there's some kind of conflict combing this flag with other flags?

[enockjeremi]

I have the same problem, is there a solution?

[azizoid]

Facing the same problem

Next.js 14.0.4
   - Environments: .env.local, .env

 ✓ Creating an optimized production build
 ✓ Compiled successfully
 ✓ Linting and checking validity of types
 ✓ Collecting page data
 ✓ Generating static pages (121/121)
 ✓ Collecting build traces
 ✓ Finalizing page optimization

[Dannymx]

Still seeing this issue in latest canary next: 14.1.1-canary.27

This issue is reproducible when you have nested dynamic params, for example in my code:

[slug]
page.tsx
    [state]
    page.tsx

The dynamicParams = false in [slug] works as expected, but in [state] doesn't throw a 404.

My solution for now is to check if the param exists against the array of strings you already have from generateStaticParams, in my example should be like this:

export default function State({ params: { state }}: { params: { state: string } }) {

const stateQuery = statesScheme.parse(cities).find((item) => slugify(item.state) === state);

if (!stateQuery) {
   notFound();
}

return <h1>{state}</h1>;

[wesnolte]

I have the same issue. It happens with a local build (okay in dev) as well as in prod. I tried your workaround and although notFound() is called I somehow still get the error!

[fadomire]

Yep the doc seems misleading:
"dynamic = 'error' changes the default of dynamicParams from true to false"

from https://nextjs.org/docs/app/api-reference/file-conventions/route-segment-config#dynamic

[freekboon]

In my case it turned out that next/headers was used in a custom hook that in turn was used in a high level component and the searchParams prop was used in the catch-all page.js. Both of which force a dynamic route which causes this exact issue. Removing the next/headers and searchParams resolved it.