-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timezone Issue #34
Comments
Hi @Mindbowser What operating system are the users that are sending the deprecated timezones on? My initial thought is that it is an outdated OS, could that be possible for the specific cohort of users? |
We don't have data as this is sent from the Mobile app and we have many users on Android and iOS, but we don't know more about device details of that user, any idea like it wont work below Android or iOS version x? |
No, Unfortunately not, I've never seen this issue. |
Ok thanks. So until we reproduce it and know the specific device we dont have solution? Any workaround?
—Please excuse typos, it’s Siri & Me using the mobile—
… On Sep 25, 2020, at 3:23 AM, patrickomeara ***@***.***> wrote:
No, Unfortunately not, I've never seen this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I am using the getTimezone function and its working fine, but suddenly for some users, we started seeing deprecated timezone IDs being stored eg. instead of getting "America/New_York" we are getting "US/Eastern", these deprecated IDs are not working on our backend Node engine, any idea how to fix this and what can be the reason?
The text was updated successfully, but these errors were encountered: