u/Simon_Huong

I think I may have found a time zone bug.
My current time zone is Taipei (UTC+8), and the app is also set to UTC+8. However, the exported SpO₂ records are stored in UTC (Greenwich Mean Time).
My sleep session was from 02:43 to 07:26 on July 19 (UTC+8), which corresponds to 18:43 to 23:26 on July 18 (UTC).
The exported SpO₂ records show measurements from 18:49 to 23:57 UTC on July 18 (confirming that SpO₂ monitoring continued for about 30 minutes after I woke up).
However, Google health consistently displays only the previous day’s SpO₂ value. For example, when the app‘s date is July 19 (UTC+8), the app only updates the value for July 18.
This makes me wonder whether the app is displaying SpO₂ without converting the timestamps from UTC to the local time zone. In other words, is it simply assigning all records with a UTC date of July 18 to July 18 in UTC+8, instead of converting them to the correct local date (July 19) before grouping and displaying them?

Why doesn’t my blood oxygen (SpO₂) reading update when I wake up each morning? It only updates the previous night’s reading after I wake up the following day.

Since updating to the latest version of Google Health, I’ve noticed several major issues when using the new Fitbit Air with my iPhone and manually starting a Hiking workout.
Before the update, every hiking session included:
GPS route map
Distance
Elevation gain/loss
After the update, all of this information has disappeared, even though I always carry my iPhone with me during hikes.
Even worse, the calorie calculations have become extremely inaccurate.
During the same hike, the calories burned while climbing uphill were almost identical to those burned while walking downhill. This makes no sense.
The average heart rate during the uphill section was 139 bpm, while the average heart rate during the downhill section was only 110 bpm. Even if the calorie calculation were based solely on average heart rate, the two values should not be this close. In reality, uphill hiking requires significantly more energy than descending.
Before this Google Health update, the calorie estimates were very similar to those from my Apple Watch and appeared to be much more accurate.
Has anyone else experienced these issues after the latest update?
Missing GPS route map
Missing distance
Missing elevation data
Highly inaccurate hiking calorie calculations
Is this a bug, or has Google changed the way hiking workouts are tracked and calories are calculated?

Since updating to the latest version of Google Health, I’ve noticed several major issues when using the new Fitbit Air with my iPhone and manually starting a Hiking workout.
Before the update, every hiking session included:
GPS route map
Distance
Elevation gain/loss
After the update, all of this information has disappeared, even though I always carry my iPhone with me during hikes.
Even worse, the calorie calculations have become extremely inaccurate.
During the same hike, the calories burned while climbing uphill were almost identical to those burned while walking downhill. This makes no sense.
The average heart rate during the uphill section was 139 bpm, while the average heart rate during the downhill section was only 110 bpm. Even if the calorie calculation were based solely on average heart rate, the two values should not be this close. In reality, uphill hiking requires significantly more energy than descending.
Before this Google Health update, the calorie estimates were very similar to those from my Apple Watch and appeared to be much more accurate.
Has anyone else experienced these issues after the latest update?
Missing GPS route map
Missing distance
Missing elevation data
Highly inaccurate hiking calorie calculations
Is this a bug, or has Google changed the way hiking workouts are tracked and calories are calculated?