Google Health faces backlash as Pixel Watch users report persistent Fitbit permission error
Google Health is once again under scrutiny as Pixel Watch owners complain about a frustrating permissions issue that refuses to disappear. The problem appears as a Fitbit-branded warning asking users to allow access to sensor data, even when the required permissions are already enabled.
The issue has sparked fresh criticism of Google’s fitness and health tracking experience, especially among users who preferred the older Fitbit app. Since the redesigned and rebranded app launched on May 19, reactions have been mixed at best. Many users have complained that the new Google Health experience feels less polished, harder to navigate, and less useful than the previous Fitbit interface.
Some Pixel Watch owners say the app looks outdated and does not present health data in a clear or convenient way. Others have taken issue with the app’s AI-powered health insights, claiming they can be inaccurate, unhelpful, or too intrusive. While some complaints are broad and light on detail, the latest permission bug appears to be a more specific and widespread concern.
The current problem centers on a recurring prompt that asks users to grant access to sensor data. For many, this warning continues to appear even after they check and confirm that every relevant permission is turned on. In some cases, the app still records sensor information normally, leading users to believe the message may be a false warning rather than an actual permissions failure.
However, not everyone is seeing normal behavior. Some Pixel Watch users report that their health and fitness data has stopped syncing altogether. That makes the issue more serious for anyone who relies on their smartwatch for step counts, heart rate tracking, sleep monitoring, workout records, and other daily health metrics.
So far, there does not appear to be a confirmed fix. Users have tried basic troubleshooting steps, including checking permissions, restarting devices, and even performing a full factory reset on the watch. Unfortunately, reports suggest that even a factory reset does not always remove the warning.
It is still unclear whether the bug affects all Pixel Watch models or only specific versions. One affected user mentioned owning the watch for more than two years, which suggests the issue may involve an older Pixel Watch model rather than being limited to the latest hardware. Still, without an official explanation, it remains difficult to know how widespread the problem really is.
The timing has led some users to suspect that the issue may be connected to a recent Google Health app update. Several reports indicate that the permission error began appearing only within the last few weeks. If the bug is software-related, Google may be able to fix it through an app update or a server-side change.
For now, Pixel Watch owners affected by the issue are left waiting. Google has not yet issued a public statement addressing the persistent Fitbit permission warning or provided an official workaround.
The situation adds to ongoing frustration around Google’s handling of Fitbit features and the broader transition to Google Health. For users who depend on consistent fitness tracking, health data syncing, and reliable smartwatch performance, a recurring permissions error is more than just a minor annoyance. It raises questions about the stability of the app and whether the current experience can match what Fitbit users had before.
Until a fix arrives, Pixel Watch users may want to keep their Google Health app and watch software updated, review app permissions, and monitor whether their sensor data is syncing correctly. If the warning continues to appear, the problem may be on Google’s side rather than something that can be solved through user settings.
