Fitbit daily health metrics missing in Google Health app, with no fix date yet

Owners of Fitbit wearables say several daily health metrics have disappeared from the Google Health app. Readings such as heart-rate variability, blood oxygen, breathing rate, resting heart rate and skin-temperature variation now show as empty in the Vitals section for many users. The problem was first picked up through social media, where several threads on Reddit describe the same symptoms. TechRadar and Android Authority both report the issue and both tie it to a recent update.

The gap seems to affect the newest readings only. Older days still show their data, and some devices still record sleep overnight. Users have pointed to Fitbit's 5.12 update as a likely trigger, after noticing the problem began around the same time. Neither outlet confirms that link. It remains a suggestion from users, not a finding from Fitbit or Google.

Several workarounds are circulating. Some people say that uninstalling and then reinstalling the Google Health app brought their metrics back. One Reddit user warned that this may be needed every morning, because the Vitals readings reset each day. Signing out and signing back in may also help. A different tip involves toggling the chart view for every metric between monthly and weekly settings. These steps worked for some users, but none is confirmed as a lasting fix.

Google has acknowledged the problem. A member of its support team told a user that the company is aware of the issue and will keep affected customers informed. The reply did not include a remedy or a date. TechRadar reports that Google has signalled a fix could take some time, and one commenter criticised the company for not resolving it faster. The sources do not show any official statement on a timeline.

The problem matters most for people who use Fitbit to track sleep, recovery or breathing and rely on the Google Health app to see those numbers each day. Anyone with a Fitbit device should check whether their Vitals readings are missing after updating the app. The sources do not say how many people are affected or which models are most involved.

Several points remain unclear. Google has not confirmed the cause, and it has not said whether the 5.12 update is responsible. No date has been given for a permanent fix. Until one arrives, users depend on the temporary steps described above.