Triggering notFound in generateMetadata results in Unhandled Runtime Error Error: NEXT_NOT_FOUND #65013
Labels
bug
Issue was opened via the bug report template.
Parallel & Intercepting Routes
Related to Parallel and/or Intercepting routes.
Link to the code that reproduces this issue
https://codesandbox.io/p/devbox/falling-water-nky943
To Reproduce
generateMetadata
for example/en/test
_
to@articleModal
fixes the issue as the parallel route doesn't exit any more.Current vs. Expected behavior
I expected to see a not found page but got an unhandled runtime error with the thrown "NEXT_NOT_FOUND_ error.
Provide environment information
Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.2.0: Wed Nov 15 21:53:34 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T8103 Available memory (MB): 16384 Available CPU cores: 8 Binaries: Node: 20.11.1 npm: 10.2.4 Yarn: N/A pnpm: N/A Relevant Packages: next: 14.3.0-canary.22 // Latest available version is detected (14.3.0-canary.22). eslint-config-next: 14.1.4 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)
Parallel & Intercepting Routes
Which stage(s) are affected? (Select all that apply)
next dev (local), next build (local), next start (local)
Additional context
Triggering notFound in generateMetadata results in
Unhandled Runtime Error Error: NEXT_NOT_FOUND
The text was updated successfully, but these errors were encountered: