Triggering notFound in generateMetadata results in Error: NEXT_NOT_FOUND when the delayed notFound call is used (e.g. fetch) #65951
Labels
bug
Issue was opened via the bug report template.
locked
Metadata
Related to Next.js' Metadata API.
Navigation
Related to Next.js linking (e.g., <Link>) and navigation.
Link to the code that reproduces this issue
https://github.com/fax1ty/next-generatemetadata-repro
To Reproduce
/en/test/id
Current vs. Expected behavior
Current: I get NEXT_NOT_FOUND in console
Desired: I see the 404 content
Provide environment information
Which area(s) are affected? (Select all that apply)
Metadata, Navigation
Which stage(s) are affected? (Select all that apply)
next dev (local), next start (local), Vercel (Deployed), Other (Deployed)
Additional context
May relate to #65013
If you remove the
setTimeout
, everything works as expectedP.S. I have created a copy of real-world project that demonstrates this problem. Perhaps the issue is something else entirely.
The text was updated successfully, but these errors were encountered: