Google's Pixel Watch has been plagued by a persistent Fitbit sensor permission bug, leaving users with a broken health tracking experience. This issue, which has been occurring since March, has affected multiple models and generations of the watch, indicating a software problem rather than a hardware fault. The bug manifests as a screen that displays the Fitbit logo and demands access to device sensors, even though users have already granted these permissions. This is particularly frustrating as it prevents users from accessing essential health tracking features such as SpO2 and skin temperature monitoring, which are crucial for sleep insights and FDA-cleared loss of pulse detection. The problem is exacerbated by the fact that the affected data is recorded in the background while users sleep, meaning they may not realize the data has stopped arriving until days later. This silent failure of the sensor pipeline is a unique challenge for health wearables, as it can lead to the loss of valuable health data. The situation is made worse by the fact that Google has not publicly acknowledged the issue, relying instead on Reddit threads for communication. This raises questions about the company's approach to device support and its commitment to user trust. While there are some steps users can take to mitigate the issue, such as keeping the watch firmware and Google Health app updated, the root cause of the problem remains unresolved. The ongoing bugs suggest that Google is still working to integrate Fitbit into its Google Health platform, and the process of folding a brand into an existing ecosystem can be disruptive. As a result, Pixel Watch owners are left with a fitness-flavored watch face, rather than the advanced health tracking device they paid for. The situation highlights the challenges of large platform migrations and the importance of effective communication with users. It also underscores the need for a more transparent and proactive approach to device support, especially for health-focused wearables. In the meantime, users are left to navigate the complexities of the issue, hoping for a resolution that will restore their trust in the device.
