This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

vo2max timezone bug in Connect web and iOS

I am consistently seeing my Vo2max logs shown for the day before the actual workout. For example, I do a workout Saturday *morning* (AEST+1100) and my watch shows a VO2Max for that day. But Connect web and iOS show the VO2max was "yesterday". The graph on Connect web has all the VO2max data points shown on the day before the respective workout.

If I do a workout on Saturday *afternoon* (AEST+1100) then the workout shows up as the correct day.

Is there a bug related to how date and timezone are used? Perhaps Connect is not taking the timezone into account and assumes US timezone even if the activity was recorded in a different timezone?

Coincidentally, timezone +1100 means that a morning workout is actually completed on the previous day in the US timezones... but an afternoon workout would be the same date but very early morning in US.