Pixel Watch permissions error fix: Google confirms work underway
A Fitbit update has knocked out SpO2 blood oxygen tracking and skin temperature monitoring on Pixel Watch devices, and Google has confirmed it is working on a fix for the permissions error. What the company has not said is when that fix will arrive, which software version caused the reset, or how many users are affected.
Owners of Pixel Watch 3 and Pixel Watch 4 devices began reporting the Pixel Watch permissions error on r/PixelWatch and r/fitbit after a recent Fitbit update, with at least one user saying the sensors had been missing for more than a week, according to Android Authority. Google's PixelCommunity account replied directly to the thread: "We regret the disruption to your health tracking experience caused by these permission resets," and confirmed that "work is underway to restore access to SpO2 and skin temperature tracking features."
These aren't trivial features. SpO2 and skin temperature are the metrics people reach for when they feel unwell or are monitoring a specific health condition. Losing them without warning, and without any timeline for restoration, is something more than inconvenience for the people who bought a health-focused wearable to use exactly those tools.
What the Pixel Watch permissions error looks like on affected devices
The symptom is consistent across reports: SpO2 and skin temperature tracking options vanish entirely from both the Pixel Watch app and the Fitbit app, with no error message and no explanation, as Android Authority reported. Users don't get a notification that permissions were reset. The features just disappear.
Both Google's PixelCommunity account and FitbitHelpCommunity attributed the disruption to a permissions reset tied to a firmware update, saying a Fitbit update Pixel Watch permissions reset had cut off app access to SpO2 and skin temperature tracking. Neither company explained the underlying technical mechanism in detail, and the root cause, whether it sits in the Fitbit app, the watch firmware, or a backend configuration, remains publicly unaddressed, per Android Authority.
Several important details are still missing. The specific software version responsible has not been identified. Whether historical health data is still visible in user accounts or has also been lost has not been addressed publicly. Google's statements have been limited to acknowledging the permissions reset and confirming work is underway.
The scope of the problem is also unclear. Reports have surfaced from Pixel Watch 3 and Pixel Watch 4 owners across at least two Reddit communities, but these are community forum posts, not a formal incident report. The actual number of affected users is unknown.
Pixel Watch permissions error fix: what affected users can try now
There is no official workaround. Google has not recommended a manual permission toggle, app reinstall, or firmware rollback, and neither PixelCommunity nor FitbitHelpCommunity has confirmed whether the eventual fix will arrive as an app update, firmware patch, or backend change, according to Android Authority.
That said, there are some reasonable steps affected users can take while waiting. First, confirm the sensors are actually missing by checking health settings directly in both the Fitbit app and the Pixel Watch app. Watch face tiles can be removed independently of the underlying feature, so a missing tile doesn't necessarily confirm the sensor is inaccessible. Go to the health settings menus in both apps to verify.
Second, make note of when the issue started relative to any recent app updates. That information may help if you end up contacting Google or Fitbit support directly, and it contributes useful context to community threads that Google's team appears to be monitoring.
On the question of factory resetting the watch: because Google has not recommended a reset and no community reports confirm it resolves the problem, it may be worth waiting for official guidance before taking that step. A reset carries its own data risks with no clear upside given current evidence. Users experiencing Pixel Watch SpO2 not working should monitor PixelCommunity and FitbitHelpCommunity for updates, as those are the channels where Google has been posting acknowledgments.
On the same note, the missing features are specifically SpO2 and skin temperature tracking. Other Pixel Watch sensors and functions appear unaffected based on available reports, so users should not assume all health readings from the watch are compromised.
Google's pattern: fast acknowledgment, slow resolution
This isn't the first time a Pixel Watch update has taken out a health or fitness feature without an immediate fix. In March 2026, four months before the current issue, a firmware update caused Pixel Watch devices to stop registering steps during certain workouts and produced erratic calorie figures, Android Authority reported. Google's community response was nearly word-for-word identical to this one: "We are aware of this issue and are working on a fix." That bug was eventually resolved, as Android Central noted.
Go back further to late 2024, and the pattern holds again. Google pulled a Wear OS 5 update for first- and second-generation Pixel Watch devices after users, including journalists, reported their watches were stuck on blank screens. The OTA rollout was paused while engineers worked on a fix, with Google committing to resume the rollout "later this year," The Verge reported in October 2024.
The common thread across all three incidents is the same: Google moves quickly to surface an acknowledgment in the community channels where complaints appear. What consistently lags is everything else. Affected software versions go unnamed. Root causes go unexplained. Workaround options are absent. Timelines are absent. For users who are actively monitoring a health condition and have built a routine around specific metrics, "work is underway" is a holding pattern, not a resolution.
The March 2026 step-tracking bug does at least establish that Google eventually closes these loops. That's a meaningful data point. But it says nothing about how long the current fix will take, and the permissions issue affecting SpO2 and skin temperature is arguably more consequential than inaccurate step counts.
What a real update from Google would look like
The current communications from PixelCommunity and FitbitHelpCommunity confirm the problem exists and that engineers are working on it. That's something. It's not enough.
A meaningful update would establish, at minimum: which software version triggered the permissions reset, so users can understand whether their device is in the affected range; whether historical SpO2 and skin temperature data has been preserved in user accounts or is at risk; what form the fix will take, whether that's an app update, a firmware patch, or a server-side change; and when, approximately, that fix is expected to ship.
None of those questions have been answered. Until at least one of them is, affected users are largely in a holding position. Watch the official PixelCommunity and FitbitHelpCommunity threads. Don't assume more disruptive interventions like factory resets will help. And treat the missing sensors as genuinely missing rather than intermittently faulty, since the evidence points to a permissions issue at the software level rather than a hardware problem. The March precedent suggests a fix is coming. The current silence from Google gives no indication of when.
Comments
Be the first, drop a comment!