Wrong Kyiv time

[bodyh93]

Here is 20:00 in Kyiv and on my android phone. But when timezone is automatic or Kyiv in Fitbit app settings, after syncing Charge 6 shows 18:00. I tried restarting phone and tracker, tried to prune all the data it install device from scratch, nothing worked. So I've set Riga timezone. But it's disappointing. By the way, Ukraine location is absent. Google devices should not have such bugs or shortcomings! What have I paid for?

[RodrigoMFitbit]

@bodyh93 Welcome to the forums. Thanks for bringing this to our attention. This is a general issue affecting some users. We will keep monitoring this situation. Thanks for reporting it. I am glad to read you have found a workaround. As soon as I have more information, I will let you know! I appreciate your patience. 

[Krond]

I tried to set up my Charge 5 and it looks like it shows GMT time for my local timezone. I tried resyncing device and choosing other timezones - when I set something like Tokyo or Tallinn I'm getting correct local time, so the problem is with Kyiv only.

My wild guess this is related to recent change in tzdata, when Kiev was renamed to Kyiv.

__________

Just to get more details on the background:

Recently ICANN group finally decided to switch spelling for Kyiv from old soviet era "Kiev" to actual spelling. However due to a number of factors the change wasn't that easy. Tzdata package provides all of the relevant data for all of the timezones for all the time being (here - signed documentary), and in case something happens to the database timezone support might go ablaze.

I guess like in 2018 I suggested to them not only to rename Europe/Kiev to Europe/Kyiv, but to create an alias from former to latter. They rejected my proposal and my approach. So now they went with just renaming, and that creates an issue with library compatibility, I already seen one on JetBrains YouTrack (reported and they fixed it). The problem happens when two apps are trying to communicate but they are using different versions of tzdata. In our case this is Android App and Device OS. When one app is trying to set a timezone it's using Europe/Kyiv timezone name, and the other one can't resolve it due to older tzdata library, defaulting to GMT time (default preference). The solution is to bump up tzdata library in all projects to be of the same version. There should be no incompatible changes as interface is quite stable through all those years.

Actually I have no idea how and why this is happening, but this description matches current issue: timezone is named Europe/Kyiv, time is shown in GMT, other timezones work fine. Just hope this details can save you some debugging time.

__________________

I guess "Ukraine location" in the app is rather a localisation preference, as when you select "Poland" you get Polish in your clock. Our preference is probably "Europe" until we hopefully can get a proper Ukrainian translation.

[PazzoMas]

Hello. I have the same issue for almost 2 years (since first pixel drop update on my pixel watch 1) and I've tried maybe almost every advice. Nothing works. I've almost got used to it. But I'll be very grateful if you manage to fix it. Thanks 

[RodrigoMFitbit]

@PazzoMas Thanks for your post and patience regarding this matter. @Krond Welcome to the forums. I appreciate your explanation in detail. I will be sharing this information with the team in charge of the Fitbit app. 

Please note that this has been reported already. In the meantime select another country that is in the same time zone, that should show the correct time on your device. I know it is not ideal, but that would be the alternate way to have the correct time on your device. I appreciate your understanding.