Fitbit users have recently run into frustrating roadblocks with their fitness trackers and the companion app. Reports are surfacing across community forums and social media detailing problems with two key functions: manually logging exercises and accessing blood oxygen (SpO2) data.
Many users, especially those using the Android Fitbit app, started noticing around April 8th that they couldn’t manually add activities. When attempting to log a workout like yoga, weights, or even simple walking – often selected directly from Fitbit’s pre-approved list – they are met with an error message.
The app prompts them to “Enter a valid activity name,” leaving users confused as they did select a valid activity. One user, sjrily, noted on the Fitbit community forums, “The add activity feature was one of the more important ones for me, but it’s become less and less useful over time.” Similarly, there are multiple other reports talking about the same issue on the official forums and on Reddit.
Fitbit support acknowledged the problem and initially suggested a temporary workaround. This involved manually typing the entire activity name exactly as listed, paying close attention to capitalization, rather than selecting the auto-filled option. However, users found this solution inconsistent at best.
Sometimes it worked, other times it failed, and certain activities couldn’t be logged regardless. Fitbit moderators have confirmed their team is aware of this bug impacting Android users and is actively working on a fix.
At the same time, another group of users found their SpO2 data unexpectedly missing. Owners of devices like the Fitbit Charge 6 and Sense 2 reported that the SpO2 tile in the app either disappeared, showed no readings, or displayed messages saying the feature was “not available” or incompatible with their tracker, even though it had functioned correctly before. User DaPash asked on the forums, “Today SpO2 is no longer available on my Charge 6…has this function been eliminated in a recent update?”
Just like the activities bug, there are multiple reports about the problem too. Moreover, Fitbit moderators have also addressed these concerns, confirming that the missing SpO2 data is due to a known bug. They stated the issue has been escalated internally and the relevant teams are working to resolve it as quickly as possible.
While Fitbit has acknowledged both the manual activity logging and SpO2 data issues and confirmed fixes are underway, no specific timeline has been given for when users can expect these problems to be resolved. So we’ll just have to wait and see how long it takes for the issues to be squashed.