Meals were showing up labeled as 'Other' instead of breakfast, lunch, dinner, or snack.
In the quiet accumulation of daily habits — what we eat, how far we run, how deeply we sleep — small errors in the tools we trust can erode confidence in our own self-knowledge. Google Health's version 5.01, rolling out this week to Android and iOS users worldwide, addresses a cluster of such errors: mislabeled meals, miscounted steps, missing sleep scores, and fractured data flows between third-party apps. It is a reminder that the infrastructure of personal wellness is only as meaningful as its accuracy, and that maintenance, however unglamorous, is its own form of care.
- Users relying on MyFitnessPal, Cronometer, and LoseIt have watched their carefully logged meals collapse into a generic 'Other' category — a small but demoralizing failure for anyone tracking nutrition with intention.
- Runners discovered their workouts mislabeled, their split data vanished, and on iOS, their step counts inflated by double-counting — turning data meant to motivate into a source of distrust.
- Sleep scores flickering inconsistently and a Today tab stuck in the past left Android users unable to get a clear picture of their own health in real time.
- Google is rolling out version 5.01 in a staggered two-week deployment, applying several fixes retroactively and signaling that a custom food creation feature is on the near horizon.
- The update also clears a long-standing Fitbit-to-Google account migration block on iOS, reopening a path that had quietly frustrated users attempting to consolidate their health data.
Google Health version 5.01 is beginning its rollout today, reaching all Android and iOS users over the next two weeks. The update targets a set of persistent bugs that have undermined the app's reliability for people tracking nutrition, exercise, and sleep.
The most disruptive fix involves meal logging from third-party apps. Entries synced from MyFitnessPal, Cronometer, and LoseIt were consistently mislabeled as 'Other' instead of reflecting their correct meal type — breakfast, lunch, dinner, or snack. That error is now corrected. The app also better handles accounts connected through multiple pathways, fills in default food names for entries imported from Apple Health, and makes unit-switching on iOS less cumbersome.
Workout tracking receives several corrections as well. Runs that were miscategorized as other exercise types have been relabeled, and the fix applies retroactively to previously logged activities. Missing split data has been restored, GPS maps load more reliably, and a bug that was double-counting steps for iOS users running both Apple Health and Mobile Track has been eliminated.
Sleep scores, which were displaying inconsistently for some users, should now appear reliably. The Android Today tab has been corrected to show current data, and nutrition and calorie charts are now consistent across all views. Improvements were also made to the Friends and Family feature on iOS, and accessibility support for VoiceOver and TalkBack users has been enhanced.
On the feature side, users can now view and log previously created custom foods, with the ability to create new ones coming soon. Guidance for setting macronutrient goals has also been added. A migration issue that was blocking some iOS users from transferring Fitbit accounts to Google accounts has been resolved as well.
The staggered rollout means version 5.01 may not appear immediately — checking back in a few days or updating manually through the app store should do the trick.
Google Health is getting a meaningful refresh. Version 5.01 begins rolling out today, and over the next two weeks it will reach all users on both Android and iOS. The update addresses a collection of bugs that have been frustrating people who rely on the app to track what they eat, how they move, and how they sleep.
The most visible fix concerns meal logging. If you've been using MyFitnessPal, Cronometer, or LoseIt and syncing those entries into Google Health, you've probably noticed something wrong: meals were showing up labeled as "Other" instead of breakfast, lunch, dinner, or snack. That's fixed now. The app also handles the situation better when the same third-party app is connected to Google Health through multiple pathways—a technical problem that was creating confusion. For people pulling data from Apple Health, the app now fills in default food names when the original entry didn't include one. On iOS, switching between measurement units while logging has been streamlined, making the process less clunky.
Workout tracking gets its own set of corrections. Some runs were being miscategorized as other types of exercise entirely; that's resolved, and the fix applies retroactively to runs already logged. Missing split data—the intermediate pace markers that runners use to understand their effort across a workout—has been restored for affected users. Maps from GPS-tracked exercises now load more smoothly, and a particularly annoying bug on iOS that was counting steps twice for people using both Apple Health and Mobile Track has been eliminated.
Sleep tracking, which has been unreliable for some users, should now display sleep scores consistently across the board. The Today tab on Android, which wasn't showing current information for some people, has been corrected. Charts displaying nutrition and calorie data are now consistent whether you're looking at the Today view, the Health section, or diving into detailed nutrition breakdowns. The app also made improvements to the Friends and Family feature on iOS, which was slow or failing to load for some users, and enhanced accessibility for people using VoiceOver and TalkBack.
One notable addition: you can now view and log custom foods you've created in the past. The ability to create new custom foods directly in Google Health is coming soon. The app also added explanations and guidance for people trying to set macronutrient goals, removing some of the guesswork from that process.
There's also a fix for a migration issue on iOS that was preventing some people from moving their Fitbit accounts over to Google accounts. If you tried before and hit a wall, the flow should work now.
The rollout is staggered, so you may not see version 5.01 immediately. Google typically spaces out app updates to catch any unexpected problems early. If you're not seeing it yet, check back in a few days, or manually update through your app store.
Citações Notáveis
Custom foods can now be viewed and logged, but adding new custom foods is coming soon.— Google Health team
A Conversa do Hearth Outra perspectiva sobre a história
Why does it matter that meal logs were labeled as "Other" instead of the actual meal type?
Because if you're tracking nutrition, you want to know whether you're eating too much at breakfast or dinner. The wrong label makes the data useless for spotting patterns in your own eating.
So these are bugs that have been around for a while?
Long enough that people noticed. The fact that Google is fixing them now suggests they were getting complaints, or the engineering team finally had time to dig into the integration layer with third-party apps.
What's the significance of the step-counting fix on iOS?
Double-counting steps inflates your activity metrics. If you're trying to hit a daily goal or understand your actual movement, bad data defeats the purpose. It's a trust issue.
Why is the custom food feature still incomplete?
Building a robust custom food system is harder than it looks. You need to handle nutrition data, storage, syncing across devices. They're letting people use what they've already created while they finish the creation tool.
Does this update suggest Google Health is becoming more reliable?
It's a sign they're paying attention to the details that matter to actual users. Whether it sticks depends on whether they keep fixing things or let new bugs accumulate.