ENVIRONMENT_FALLBACK

[Emiliano-Bucci]

After upgrading to latest version (3.1.4) I've started to get this error
s [Error]: ENVIRONMENT_FALLBACK
code: 'ENVIRONMENT_FALLBACK',
during static build generation (all my pages exports getServerSideProps) so I guess it could be the 404 page (?)

The stack trace is -> /node_modules/use-intl/dist/production/react.js:1:1332

Any clues?

[TudorStegarescu]

The same issue with 3.2.4 (timeZone is defined in getRequestConfig)

[amannn]

This might be relevant for you from the time zone configuration docs:

The time zone in Client Components is automatically inherited from the server side if you wrap the relevant components in a NextIntlClientProvider that is rendered by a Server Component. For all other cases, you can specify the value explicitly.

[TudorStegarescu]

based on documentation i cannot see requirements to wrap in NextIntlClientProvider, it was mentioned if we like, but not required.

[TudorStegarescu]

by adding timeZone prop to NextIntlClientProvider solved issues.
thanks @amannn

[brookslyrette]

I'd expect a null timezone to not error and just inherit the servers timezone.

[amannn]

From the time zone docs:

The time zone in Client Components is automatically inherited from the server side if you wrap the relevant components in a NextIntlClientProvider that is rendered by a Server Component. For all other cases, you can specify the value explicitly.

Does that help?

[Ncookiez]

The docs make it seem like this is an option. If you don't specify a timezone you get that error.

Even in the prop descriptions:

I am OK with using the user time zone in this scenario. The error should not be displayed.

[appleseed-iii]

doing this works

const timeZone = Intl.DateTimeFormat().resolvedOptions().timeZone;
return (
  <NextIntlClientProvider timeZone={timeZone}>