`RangeError: Invalid time zone specified:` error caused by usage of `formatInTimeZone` function for some folks about date-fns-tz HOT 7 OPEN

Same issue happening for me in react native

from date-fns-tz.

I just had this error thrown. After wrestling with it for hours and tracing the issue to the same line as OC, I realized/found the problem was not with my timezone parameter, but with my date string (the first parameter) which was a string. I don't know why this error was getting thrown in my case, but it was very misleading for the error to flag where it did with the message it did. After changing to a UTC epoch timestamp (number), I haave has zero problems, including the timezones all of the above commenters have listed.

from date-fns-tz.

Still facing the same issue for this Timezone: Asia/Kolkata, Any update or workaround for this?

from date-fns-tz.

We are having the same issue in React Native for Asia/Kolkata

from date-fns-tz.

After doing some research, my impression is that Intl.DateTimeFormat is system specific, and the Asia/Kolkata issue only happens on iOS (at least based on the errors we have seen in Sentry).

Based on facebook/hermes#1100, we decided to manually map Asia/Kolkata to Asia/Calcutta in our code before passing the timezone to date-fns-tz. And that seemed to have helped.

from date-fns-tz.

Here we are having the same issue with America/Sao_Paulo and America/Cuiaba timezones

from date-fns-tz.

having the same issue with Africa/Johannesburg

from date-fns-tz.