Skip to content
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

Open
Mindbowser opened this issue Sep 24, 2020 · 4 comments
Open

Timezone Issue #34

Mindbowser opened this issue Sep 24, 2020 · 4 comments

Comments

@Mindbowser
Copy link

Mindbowser commented Sep 24, 2020

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?

@patrickomeara
Copy link
Member

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?

@Mindbowser
Copy link
Author

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?

@patrickomeara
Copy link
Member

No, Unfortunately not, I've never seen this issue.

@Mindbowser
Copy link
Author

Mindbowser commented Sep 24, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants