[Android] Wrong date is saved for a tick
|
|
When I add a tick it selects current date as a default, let's say June 24th. After the tick is saved the date becomes June 23th. |
|
|
Seeing the exact same issue on the iOS app: all tick dates are shown as one day off. |
|
|
Thanks folks, we're looking at this now. |
|
|
Can confirm this is still happening, months later Edit: I'm actually seeing a post suggesting this has been going at least a couple years now... |
|
|
I thought I read somewhere in the past that wrong timezones is used. E.g. utc is used instead of local or similar and why sometimes you get the day before depending on where you live. Maybe be wrong of course but a classic issue. |
|
|
I guess I made same comment here last year: |
|
|
I had a gut feeling it might be an error like that but dismissed it as too easily fixable to have stayed around for years like this problem has. |
|
|
Nick Wilderwrote: Thanks folks, we're looking at this now. Any update? I can confirm this is still happening as of 10/03/20 (or as my app likes to think, 10/02/20) |
|
|
11/1/20 still an issue |
|
|
Nick is asking for help about this here: |



