Wrong time for current location is timezone does not match

[Victor Thompson]

If the user sets their timezone in the System Settings to be different from the timezone of the "Current Location" specified in the app, the time of the "Current Location" is assumed to be that of the timezone specified in the settings.

[Victor Thompson (vthompson)]

In the attached screenshot it can be seen that the "Current Location" city of Minneapolis is assumed to be a different timezone from the correct instance in the world cities. Either "Current Location" needs to assume the timezone specified in settings or it needs to allow for the timezone of the selected city to be used.

[Bartosz Kosiorek (gang65)]

Hello Victor.
Could you please check if this issue is reproducible with current Clock version?

[Victor Thompson (vthompson)]

Hi Bartosz,

This bug is no longer valid because there is no "Current location" time being displayed. The saved cities all work as expected.

One thing to note is that when the time zone is changed in the System Settings (with the app open) the app adjusts the time incorrectly and is incorrect until the app is restarted.