![\"google](\"https:\/\/www.newsbeep.com\/uk\/wp-content\/uploads\/2026\/03\/google-pixel-watch-4-app-grid-launcher.jpg\"\/ "\\"google")
<\/p>\n<\/p>\n
Rita El Khoury \/ Android Authority<\/p>\n
TL;DR<\/p>\n
Some Pixel Watch owners say SpO2 and skin temperature tracking stopped working after a recent Fitbit update.
\nGoogle and Fitbit have acknowledged the permission reset issue and say work is underway to restore access.
\nReports include both Pixel Watch 3 and Pixel Watch 4 users, but it\u2019s unclear how widely the bug is affecting owners.<\/p>\n
Google launched the Fitbit Air yesterday, giving its wearable lineup a fresh screenless tracker and a new entry point into its revamped health platform. But the company is also getting some less welcome feedback from another corner of its wearable ecosystem, as some Pixel Watch owners say a recent update has broken SpO2 and skin temperature tracking on their current devices.<\/p>\n
The issue was raised in a Reddit thread on r\/PixelWatch<\/a>, where a Pixel Watch 3 owner said a recent Fitbit update had reset permissions for skin temperature and SpO2 tracking. The user said they couldn\u2019t simply turn the permissions back on, as the permissions page showed that no app was requesting them. A few other commenters reported similar problems in the thread.<\/p>\n Don\u2019t want to miss the best from Android Authority?<\/p>\n Google\u2019s PixelCommunity account responded in the thread<\/a>, acknowledging \u201cWe regret the disruption to your health tracking experience caused by these permission resets.\u201d It added that \u201cwork is underway to restore access to SpO2 and skin temperature tracking features.\u201d<\/p>\n A separate r\/fitbit<\/a> thread suggests the issue isn\u2019t limited to the Pixel Watch 3. In that post, a Pixel Watch 4 owner said the same sensors had stopped appearing in the Pixel Watch and Fitbit apps for more than a week. FitbitHelpCommunity later replied<\/a> with almost the same message, again pointing to the same firmware update and saying work is underway to restore access.<\/p>\n We don\u2019t know how widespread this issue is, and the user in the Fitbit thread appears to have rectified it by restarting their device. However, the official replies make clear that Google and Fitbit are aware of a real permissions-related issue tied to the recent update, which isn\u2019t ideal timing given that Google is trying to convince more people to buy into its health-tracking ecosystem.<\/p>\n![\"google](\"https:\/\/www.newsbeep.com\/uk\/wp-content\/uploads\/2026\/01\/1768240152_738_google_preferred_source_badge_light@2x.png\"\/ "\\"google"){kind=icon}
![\"google](\"https:\/\/www.newsbeep.com\/uk\/wp-content\/uploads\/2026\/01\/1768240152_238_google_preferred_source_badge_dark@2x.png\"\/ "\\"google"){kind=icon}
<\/a><\/p>\n