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
Note: I'm in the America/Vancouver timezone, so the output may be different for people in different timezones. To repro this reliably, you must be in the America/Vancouver timezone.
In the above snack, the correct timezone (America/Vancouver) is calculated with getLocalizationAsync and Intl.DateTimeFormat().resolvedOptions().timeZone. When using Localization.getCalendars(), I get America/Adak, which is 2 hours behind my current timezone.
Thank you for filing this issue!
This comment acknowledges we believe this may be a bug and there’s enough information to investigate it.
However, we can’t promise any sort of timeline for resolution. We prioritize issues based on severity, breadth of impact, and alignment with our roadmap. If you’d like to help move it more quickly, you can continue to investigate it more deeply and/or you can open a pull request that fixes the cause.
Minimal reproducible example
https://snack.expo.dev/MlFZ4YUTbA
Summary
Affected platforms: web
Note: I'm in the
America/Vancouver
timezone, so the output may be different for people in different timezones. To repro this reliably, you must be in theAmerica/Vancouver
timezone.In the above snack, the correct timezone (
America/Vancouver
) is calculated with getLocalizationAsync andIntl.DateTimeFormat().resolvedOptions().timeZone
. When usingLocalization.getCalendars()
, I getAmerica/Adak
, which is 2 hours behind my current timezone.Environment
The text was updated successfully, but these errors were encountered: