[Bug] Fasting clock does not show proper 24-hour time
Cronometer beta version 3.3.0
Device: Google Pixel 3
OS: Android 10
I have set up the following fasting time through web application (beta.cronometer.com).
Fasting duration: 20 hours
Fasting start date: 17 Oct 2019
Fasting start time: 22:16
Fasting end date: 18 Oct 2019
Fasting end time: 18:16
When I view the fast on the phone app, this is what shows:
Issue: The phone app shows 10:16 and 6:16 instead of the correct 24-hour times.
The fasting countdown is still correctly showing that the fast is in progress.
Comments
-
Thanks Vickie! We have reproduced the issue and reported it to the dev team
Hilary
cronometer.com
As always, any and all postings here are covered by our T&Cs:
https://forums.cronometer.com/discussion/27/governing-terms-and-disclaimer -
A very possibly related issue so I didn't start a new thread.
If I create a fast through the Android phone app using start times such as 21:30, 23:00, etc, on saving and returning to view it would become 00:30 and 00:00, and inform me that the fast has completed when it should still be in progress and so on.
This cannot be reproduced if the fast was first created on the web app and viewed on the phone app. The issue in that case is what was reported above in the original thread.
-
@Vickie oh yeah it looks like it is viewing the time as the "am" time so it has "completed" according to what it knows. Definitely looks related! I'll pass it along
Hilary
cronometer.com
As always, any and all postings here are covered by our T&Cs:
https://forums.cronometer.com/discussion/27/governing-terms-and-disclaimer