Is Google Health App Down? Pixel Watch Users Hit by Fitbit Permissions Bug
If you're trying to find out whether the Google Health app is down, the short answer is: not broadly. What's actually happening is narrower and, for affected users, more frustrating. A Fitbit-branded permissions screen is looping on Pixel Watch devices, blocking access to health apps and, in some cases, stopping data from syncing entirely. Google has not issued a public statement, and no user-side fix has been confirmed.
Reports started surfacing on r/PixelWatch over the weekend of July 12-13, spanning multiple Pixel Watch generations, Techgenyz reported yesterday. The Google Health Status Dashboard lists an active incident under "Device Sync / Pairing" covering July 14-15, last updated at 06:39 PDT this morning, though the entry does not explicitly name the Pixel Watch permissions error.
Is the Google Health app down?
Not across the board. Based on Google's status page and current user reports, the app is functioning for most users. The issue appears confined to a Fitbit sensor permissions bug affecting some Pixel Watch owners, with variable impact: some affected devices continue logging data normally while others have stopped syncing altogether, per Notebookcheck.
The status dashboard entry is worth watching, but treat it as suggestive context rather than confirmation that the permissions bug and the Device Sync incident share the same root cause.
What the Pixel Watch Google Health permissions screen bug actually looks like
The bug surfaces as a looping screen bearing the Fitbit logo, demanding sensor access. Dismissing it or tapping through does nothing. It comes back. The catch: users report every permission the prompt requests is already enabled on both the watch and the paired phone, per Techgenyz.
Because reports span multiple Pixel Watch hardware generations equally, a device-specific fault is unlikely. The timing and breadth both point toward a recent app update as the probable trigger, though no specific version has been confirmed, Notebookcheck noted yesterday.
The prompt alone doesn't tell you much about your actual data. Some users seeing the warning report that health tracking continues normally in the background; others say syncing has stopped entirely. Four things worth checking now:
- Is the Fitbit permissions prompt appearing on your watch and refusing to clear?
- Can you open health apps on the watch, or does the screen block access entirely?
- Do your Google Health charts on your phone show recent heart rate, steps, and sleep data, or are there unexplained gaps?
- Is SpO2 or skin temperature data still arriving from the past few nights?
If the data is still flowing, the prompt may be a cosmetic false alarm for your device. If the charts show gaps, the disruption is functional, not cosmetic.
What to do about the Google Health app not working on Pixel Watch
No user-side fix has been confirmed as of today. Closing and reopening the affected app is worth a quick try first. A structurally similar sensor permissions bug in May cleared for some users with that step alone, Techgenyz reported, though there is no confirmation the same approach is working for this incident.
Skip the factory reset. Several users who performed a full wipe of their Pixel Watch reported no improvement afterward, per both Techgenyz and Notebookcheck. When a reset fails to clear an error, the problem almost certainly lives in Google's app code or backend systems rather than the device itself. No amount of adjusting local settings will resolve that, Techgenyz noted.
One thing worth doing while waiting for Google to act: check your sleep charts manually, specifically SpO2 and skin temperature readings from the past several nights. These are recorded passively during sleep with no alert when they stop. You find out days later, open the app, and see an empty chart with no way to recover what was missed, according to Techgenyz. That data is simply gone.
For ongoing updates, monitor the Device Sync / Pairing entry on the Google Health Status Dashboard and watch r/PixelWatch. Based on how earlier incidents played out, an acknowledgment from Google's PixelCommunity account is likely to appear in a community thread before any formal support page is updated, Techgenyz reported.
Why this fits a familiar pattern since the Google Health rebrand
The current bug is the latest in a run of sensor and sync failures that have hit Pixel Watch users since Google rebranded Fitbit as Google Health in May. The rebrand launched to enough complaints that Google published a public fix roadmap within days, a list running to more than 39 items covering mislabeled workouts, over-reported calorie burn, and food logging failures, PhoneArena reported about six weeks ago.
That roadmap clearly did not cover everything. Four months earlier, a separate bug zeroed out step totals during aerobic workouts while producing wildly inflated activity figures. Some users saw steps, distance, and calories double or triple on days they barely moved; one user was credited with burning between 6,000 and 7,000 calories in a single day, Techgenyz reported.
Then, around the time of the rebrand, a firmware update quietly reset SpO2 and skin temperature permissions across multiple Pixel Watch generations. Users couldn't restore them because the permissions interface showed no app as requesting access, making the interface itself the obstacle. Google's PixelCommunity account acknowledged that incident on Reddit before any formal support documentation was updated, per Techgenyz.
The current bug looks structurally close to that earlier incident: a permissions layer misbehaving across hardware generations, with community threads surfacing the problem before Google says anything officially. That communication pattern has held across every major incident since the rebrand.
What to watch for next
Google has not publicly commented on the current bug, per both Techgenyz and Notebookcheck. This is at minimum the third sensor-related permissions or sync failure to hit Pixel Watch health features since the Google Health rebrand launched less than two months ago.
For affected users, the practical signals to monitor are changes to the Device Sync / Pairing entry on the Google Health Status Dashboard and any response from Google's PixelCommunity account in the active r/PixelWatch thread. Based on the pattern from earlier this year, that Reddit acknowledgment will come before anything reaches an official support page, Techgenyz noted. In the meantime: check your sleep data for gaps, don't bother with the factory reset, and don't expect a fix that originates on your end.
Comments
Be the first, drop a comment!