You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use the notFound and i18n features on SSG pages with enabled fallback (blocking strategy). Variables locale and locales are undefined in getStaticProps context when notFound occurs. This happens only when an app is deployed to Vercel.
This ensures we provide the current `locale`, `locales`, and `defaultLocale` in the context when rendering the 404 for a blocking SSG page
Fixes: #18505
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.
vercel
locked as resolved and limited conversation to collaborators
Jan 29, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug report
Describe the bug
I use the
notFound
andi18n
features on SSG pages with enabled fallback (blocking
strategy). Variableslocale
andlocales
areundefined
ingetStaticProps
context whennotFound
occurs. This happens only when an app is deployed to Vercel.To Reproduce
Repository: next.js-bug-i18n-not-found
Steps to reproduce the behavior:
Expected behavior
Displaying
Screenshots
N/A
System information
Additional context
Works fine locally in dev and prod modes.
The text was updated successfully, but these errors were encountered: