What the Google Health app bug blitz is fixing
The Google Health app bug blitz refers to a rapid series of software updates that target widespread user complaints about broken Fitbit migration, unreliable fitness metrics, and inconsistent nutrition and sleep data, aiming to repair trust in Google’s newly redesigned health platform. After a rocky rollout of version 5.0, Google is now pushing version 5.01 on Android and iOS with more than 15 core bug fixes spanning nutrition tracking, workout data accuracy, sleep score issues, and the Fitbit account transfer experience. User reaction to the redesign was negative enough that Google publicly promised “big changes over the next few weeks and months”, and this release is the first sign of that longer roadmap. The company is focusing less on flashy new features and more on making existing health and fitness data reliable enough to support day‑to‑day use.
From backlash to version 5.01: Google’s first major response
Google Health’s first post‑redesign update is unusually large for a 5.0 to 5.01 jump, with at least 16 notable changes listed across nutrition, fitness, and sleep. According to Droid Life, this is the first “big Google Health app update” following user backlash and a community promise that Google would roll out big changes in the coming weeks and months. On Android, the Today tab now shows more up‑to‑date information instead of stale cards, while both platforms benefit from accessibility improvements for VoiceOver and TalkBack users. The rollout is staggered, with Google noting that availability may vary by device and carrier as the update propagates. While the feature list is modest, the scale of bug fixes signals that Google is treating early criticism as a priority and using 5.01 as a foundation for more ambitious upgrades that it has already teased for future releases.
Nutrition tracking fixes and custom food logging
Nutrition is one of the biggest winners in Google Health 5.01, with several nutrition tracking fixes aimed at making daily food logs more reliable. Users can now view and log previously created custom foods that were already in their accounts, a popular request from people migrating from Fitbit’s ecosystem. New custom food creation is still missing, but Google says it is “coming soon” in a future update. The app now includes macronutrient goal guidance, giving clearer explanations when users set protein, carb, and fat targets. Import problems from third‑party services like MyFitnessPal, Cronometer, and Lose It have also been cleaned up, so meals no longer appear under a generic “Other” category when shared via Apple Health. On iOS, switching between measurement units while logging is smoother, and nutrition and calorie charts now align across the Today, Health, and deeper nutrition views.
Workout data accuracy and sleep score issues
Fitness and sleep tracking were another pain point for early adopters, leading to a cluster of fixes around workout data accuracy and sleep score issues. Runs that had been mislabeled as other workout types are now corrected, and Google says both new and historical runs should show the right workout labels. Missing split information in some run summaries has been restored, while GPS‑based workout maps now load more reliably instead of hanging on loading states. On iOS, a bug that caused steps to be counted twice when both Apple Health and Mobile Track were enabled has been fixed. Sleep tracking also sees a key improvement: a glitch that prevented some users from seeing sleep scores in the Sleep tab has been resolved, bringing back one of the most visible metrics for people migrating from Fitbit’s sleep analysis.
Fixing Fitbit account transfers and what still needs work
Beyond raw tracking bugs, one of the most important changes in this wave is for Fitbit account transfer and migration. Android Authority reports that 5.01 resolves Fitbit‑to‑Google account migration failures on iOS, an issue that left some users stuck between platforms and unable to see their historical data in the Google Health app. The update also speeds up slow‑loading Friends and Family screens and tightens Fitbit integration behaviour in the background. Still, several gaps remain. Users cannot yet add new custom foods, even though they can log existing ones. Google has only started to address broader complaints about tile density, interface clutter, and the heavy emphasis on AI suggestions. The company has already previewed a larger roadmap of changes coming over the next few months, so this bug fix blitz looks more like a stabilising phase than a final destination.
