Fitbit users can’t see Google Health metrics after update – how to fix it

Fitbit users are reporting that several core health metrics have stopped appearing in the Google Health app, and the trouble appears to have started around a software update. According to discussion among users on Reddit, the problem shows up after installing Fitbit update 5.12. One user said that a Fitbit Air device stopped tracking metrics in the Vitals section of the app, listing breathing rate, blood oxygen, resting heart rate, heart rate variability (HRV) and skin temperature among the missing figures. Multiple people in the same thread said they had run into the same behavior over the previous few days.
Google has confirmed it is aware of the problem. In a customer support reply, the company said it is working to identify a resolution as quickly as possible. Google did not immediately respond to a request for comment from the publication that covered the reports. The timing has drawn complaints: some users say the bug has been visible in the app for roughly six days, and at least one person in the thread questioned why a company of Google's size and engineering resources had not yet fixed it.
The affected metrics are exactly the ones a health wearable is usually bought for. Resting heart rate, HRV, breathing rate, blood oxygen and skin temperature are the signals that feed into recovery and readiness views, and they are the numbers Fitbit users check daily rather than occasionally. When the Vitals panel comes up empty, the watch is still likely collecting raw data, but the app is failing to surface it. That distinction matters for anyone trying to figure out whether the device or the software is at fault. A missing readout in the app is a display or sync problem; a missing recording on the device would be a hardware or sensor problem, and nothing in the reports points to the latter.
For now, users have circulated three workarounds in the thread. The first is to log out and log back in. The second is to uninstall and reinstall the app. The third, which several people said worked, avoids both: open each statistic that is failing to populate and switch it to the monthly view. According to the user who suggested it, doing this repopulates the main screen with the latest information without a logout. In practice, that third option is the least disruptive, because reinstalling an app can mean re-pairing a device and re-granting permissions, and a logout can disturb account state on a phone.
This suggests a straightforward read on what is happening, though it is inference rather than anything Google has stated. A bug that can be cleared by opening the monthly view for an individual metric points to a caching or refresh fault in how the app pulls data from the cloud and fills the summary screen. The call to the monthly view forces a fresh request for that stat, and once the data arrives the main panel redraws. That kind of bug would be introduced by a client-side change in how the app fetches or renders data, not by a problem with the wearable's sensors. The correlation with version 5.12 fits that picture: a release that changed the data pipeline would explain why metrics vanished for users who updated and why the device keeps recording normally.
Two caveats are worth flagging. The link to version 5.12 comes from users speculating on Reddit, not from an official Google statement, so users who have not updated may still be affected and the version number should be treated as a strong lead rather than a confirmed cause. And because workarounds clear the display temporarily, the underlying fault may return on the next sync until a patched build ships.
Fitbit's health data now lives in the Google Health app following the migration of Fitbit accounts into Google's ecosystem, so a display bug here touches every user who checks vitals through that app rather than through the older Fitbit interface. That makes a small-seeming rendering fault a visible, daily annoyance for a large installed base, and it is why a six-day gap has drawn public frustration.
Why it matters: Developers and product teams building on or alongside wearables should read this as a reminder that sync and rendering layers fail independently of sensors, and that a cache-clearing interaction in the UI can mask a bug that still exists in the pipeline. Users affected today are consumers of health metrics, but the same class of fault can hit any app that assembles device data into a dashboard, which makes post-update verification of the fetch-to-render path worth building into release checks. How quickly a fix lands will also shape how much trust those users place in the Google Health app going forward, an outcome that remains to be seen.
Based on reporting from the original publisher. Visit the source for full context and later updates.
Publisher excerpt
Google says it’s working on a fix – meantime, users have found workarounds.