Google Health App 5.01: Update Restores Accuracy to Food Logging, Run Tracking, Sleep Scores and Fitbit Migration

Table of Contents

1. Key Highlights
2. Introduction
3. What the 5.01 update brings to nutrition tracking
4. How the update fixes food‑logging integration problems
5. Fitness and activity tracking: what was broken, what’s fixed
6. Sleep tracking: sleep score reliability restored
7. Account migration, Friends & Family and Today feed fixes
8. Accessibility and platform parity
9. What this update means for user trust and data integrity
10. How to update, verify fixes and troubleshoot lingering issues
11. Practical recommendations for users who rely on Google Health daily
12. What the update does not (yet) deliver
13. How this fits into the broader health app ecosystem
14. Privacy and data governance: practical considerations
15. Developer and partner implications
16. What to expect next: likely priorities for upcoming updates
17. Real‑world scenarios: how 5.01 changes day‑to‑day use
18. Measurements to watch after updating
19. FAQ

Key Highlights

• Google Health 5.01 adds view-and-log support for previously created custom foods, macronutrient goal guidance, and fixes multiple food‑logging integration issues from MyFitnessPal, Cronometer and Lose It.
• The update resolves fitness tracking errors — mislabeled runs, missing split data and unreliable GPS map loading — and fixes duplicated step counts on iOS and missing sleep scores.
• Reliability and usability improvements address Today‑feed staleness, Fitbit-to‑Google account migration failures on iOS, slow Friends & Family screens, and accessibility for VoiceOver and TalkBack.

Introduction

Google has released version 5.01 of the Google Health app for Android and iOS, marking the first post‑redesign update since the product’s rebrand. The release focuses less on flashy new features and more on restoring trust in day‑to‑day tracking: nutrition logging is clearer, workout data is more accurate, sleep scores reappear, and several cross‑platform integration headaches have been addressed.

Users and clinicians depend on consistent, correctly labeled data when making decisions about training plans, dietary adjustments, or clinical follow‑ups. Small errors — a run recorded as a bike ride, a meal placed in the wrong category, or duplicate step counts — can erode confidence. This update targets those exact pain points and provides utility improvements that matter most to people who rely on the app daily.

The rollout begins now and will expand over the coming week, varying by device and carrier. The following analysis expands on what changed, how those changes affect real‑world users, and what still matters when you next open the app.

What the 5.01 update brings to nutrition tracking

A visible change in 5.01 is improved handling of custom foods and clearer guidance around macronutrient goals. Users who already created custom foods outside the app can now view and log those entries directly in Google Health. The ability to create new custom foods from inside the app remains pending; Google says that capability will arrive in a future release.

Macronutrient goal guidance is another practical addition. For many people, setting targets for protein, carbohydrates and fats is unfamiliar territory. Small, contextual explanations linked to goal settings reduce the guesswork. For instance, a recreational runner who wants to prioritize recovery can now find guidance on what proportion of calories should come from protein versus carbohydrates and adjust targets accordingly.

Integration with third‑party food logging services has also been tightened. Users who rely on MyFitnessPal, Cronometer or Lose It to catalogue meals previously reported problems where imported entries would appear under the ambiguous “Other” meal type rather than Breakfast, Lunch, Dinner or Snack. That mislabeling makes trends harder to interpret — for example, calorie distribution across meals — and compromises any automated alerts or goal comparisons that depend on meal type. The update corrects those mappings and improves how duplicate logs are handled when the same service is connected through multiple paths, such as both Health Connect and a direct integration.

Real‑world example: an office worker who prepares breakfasts at home and logs them in MyFitnessPal found entries showing up under “Other.” That made it difficult to track whether they were actually hitting a breakfast calorie target aimed at avoiding mid‑morning snacking. With the fix, those same entries map to Breakfast and the nutrient charts show an accurate distribution.

Other quality‑of‑life changes include default names for unnamed food logs coming from Apple Health and easier switching of measurement units when entering items on iOS. Google also harmonized nutrition and calorie charts so they appear consistent across Today, the Health overview and the nutrition deep dive screens.

Practical advice

• If you have custom foods created elsewhere, update the app and attempt to log them — they should now appear for selection.
• If you see duplicated food entries after connecting the same third‑party app multiple ways, disconnect redundant connections in Health Connect or the Google Health app until you confirm deduplication behavior.
• Revisit your macronutrient goals using the new guidance to ensure targets match activity levels and personal goals.

How the update fixes food‑logging integration problems

Third‑party integrations create complexity because data may flow through multiple intermediaries. Health Connect functions as a hub to move data between apps, while many services also offer direct API integrations with Google Health. When the same source feeds data through both channels, the result can be duplicated entries or conflicting metadata — meal type, portion size, even timestamps.

5.01 addresses several of these practical failure modes:

• Meal types imported via Apple Health from MyFitnessPal, Cronometer and Lose It are now mapped correctly to specific meal categories.
• The app recognizes when the same meal log arrives from multiple integrations and handles duplicates more intelligently.
• Unnamed food logs imported from Apple Health receive default titles so they remain identifiable.

These fixes make the app more tolerant of the messy reality of real‑world syncing.

Real‑world example: an active parent logging family meals in Cronometer while using an iPhone and a Wear OS watch experienced repeated entries and wrong meal labels because Cronometer sent data into Apple Health and Cronometer’s separate Google Health connection relayed the same meal again. The update’s improved deduplication reduced duplicate items and restored the meal breakdown in Google Health’s daily summaries.

Technical considerations

• Deduplication often requires robust matching heuristics: timestamp comparisons, nutrient fingerprints (calories + macronutrient totals), and unique meal IDs when available. Users should expect deduplication to improve incrementally rather than be perfect immediately.
• If you still see duplicates after updating, temporarily disconnect and then reconnect the third‑party service to force a fresh sync with the corrected mapping rules.

Fitness and activity tracking: what was broken, what’s fixed

Several fitness tracking issues made the update necessary. The most visible problems were runs mislabeled as other workout types, missing split data in run summaries, and intermittent failures when loading GPS‑based workout maps.

Mislabeled workouts create practical problems. A structured training plan that relies on run volume will undercount running distance if some sessions are categorized as “Other” or as cycling. Splits matter to runners and coaches; missing split times prevent analysis of pacing, interval effectiveness and fatigue patterns. Maps failing to load dull the post‑workout review experience and make it harder to confirm route, distance and elevation.

5.01 addresses these points:

• Runs are now consistently labeled as runs, including historical entries that previously appeared miscategorized.
• Split data that disappeared from some summaries has been restored.
• GPS workout maps load more reliably, improving post‑activity analysis.

Real‑world example: a marathoner reviewing weekly training noticed a tempo run recorded as a generic workout; without splits, they couldn’t see whether the target pace was sustained. After updating to 5.01, the session showed as a run with correct splits and the coach could verify pace consistency.

iOS mobile step counting duplication Some iOS users experienced double counting of steps when both Apple Health and Google Health’s Mobile Track function were active. Mobile Track uses device motion sensors to count steps natively. When Apple Health also supplied step data, users with both sources enabled saw inflated step totals.

5.01 corrects this behavior so steps are not double‑counted for users who had both sources enabled. That matters for people using step goals as a simple activity metric, for employers using step‑based wellness incentives, and for research that aggregates population step counts.

Practical steps for runners and casual exercisers

• After updating, open a recent workout and verify the activity type, splits and GPS map. If issues persist, force a sync or re‑save the exercise.
• For runners who use multiple devices or apps, configure a single source of truth for workout uploads to avoid future duplication (for example, upload runs to a single service and allow Health Connect or Google Health to pull from there).
• If you rely on cadence or elevation data, check the detailed workout view to confirm those metrics persist after correction.

Sleep tracking: sleep score reliability restored

Sleep scores are a shorthand metric many users rely on to assess nightly recovery. When the Sleep tab stopped showing scores for some users, it reduced the app’s immediate utility as a sleep‑insight tool.

5.01 resolves the issue that prevented sleep scores from appearing. Restoring this metric permits users to monitor trends and correlate sleep quality with activity, calorie intake and mood.

Practical considerations for sleep tracking

• Sleep scores are algorithmic and can fluctuate as detection algorithms change. Short‑term variations should be interpreted alongside trends over weeks.
• If you use an external tracker (Fitbit or another device) for sleep, confirm that data is successfully syncing into Google Health after updating.
• Nightly disturbances logged by a partner app may not immediately reflect in aggregate sleep scores; check raw timelines for a fuller picture.

Account migration, Friends & Family and Today feed fixes

One of the more consequential fixes affects users migrating Fitbit data to a Google account on iOS. The migration flow previously blocked some users from completing the move. Google says restarting the migration flow after updating will allow users to carry out the account transfer.

Friends & Family screens on iOS that were slow or failed to load have been sped up or made reliable. These changes restore social features that people use to share progress, support commitments and compare activity with peers and family.

On Android, the Today tab had problems showing up‑to‑date information for some users. The update corrects that so daily summaries reflect recent activity and nutrition logs.

Real‑world example: someone who relied on Fitbit for sleep and heart‑rate history tried to migrate to a Google account and was blocked midway through the transfer. After applying the update and following the migration flow again, their Fitbit data migrated and populated in Google Health’s timeline.

Migration best practices

• Back up any critical data or export histories if possible before starting migration.
• Ensure both the Fitbit app and Google Health are up to date before initiating transfer.
• If migration fails again, attempt the flow on a different device or network, and contact support with screenshots of error messages.

Accessibility and platform parity

The update includes improvements for VoiceOver on iOS and TalkBack on Android. Buttons and charts received enhancements that make the app more navigable for users relying on screen readers. Accessibility changes like meaningful labels, focus order fixes and improved audio descriptions reduce friction.

Platform parity remains a common complaint for multi‑platform apps. 5.01 narrows some gaps — for example, measurement switching in iOS logging and consistent nutrition charts across platforms — but differences persist. Google appears to prioritize restoring core functionality first, then tidying cross‑platform experience.

What accessibility improvements mean in practice

• Users relying on screen readers should find the app’s main actions and charts easier to reach and interpret.
• Developers of third‑party apps integrating with Google Health should test for correct metadata and labels to ensure their data is usable for assistive technologies.
• These changes reduce the cognitive load for users who cannot interact with standard touch targets.

What this update means for user trust and data integrity

Small tracking errors accumulate into big credibility problems. When logged meals vanish into “Other,” or runs lose splits, users stop relying on the app for training, dietary planning or clinical monitoring. Fixing those errors rebuilds confidence and reduces friction for people who use digital health tools for daily self‑management.

Data integrity goes beyond single fixes. It relies on:

• Correct labeling and mapping of imported data.
• Effective deduplication across integration paths.
• Robust handling of historical records.
• Transparent error handling and clear recovery flows (for example, account migration).

Google’s 5.01 release addresses all four areas to some extent. Restoring past runs to the correct activity type preserves historical continuity. Improved mapping of meal types and deduplication prevents obvious analytical errors. Resolving migration and Today‑feed problems enables users to access a complete, up‑to‑date dataset.

Real‑world consequence: a coach using Google Health to monitor an athlete’s training load will now receive more reliable weekly totals and correct run-type classification, enabling safer load progression and better-informed coaching decisions.

How to update, verify fixes and troubleshoot lingering issues

Update procedure

1. Open the App Store or Google Play Store and update Google Health to the latest version.
2. After installation, open the app and allow any required permissions (location for GPS maps, Health Connect or Apple Health permissions for third‑party data).
3. Restart the app and check Today and each data category (Nutrition, Activity, Sleep) to confirm changes have applied.

Verification checklist

• Nutrition: confirm a previously misclassified entry now appears under the correct meal type. Look for default names on unnamed imported items.
• Fitness: open a recent run and verify the activity is labeled as “Run,” splits are visible, and the GPS map loads.
• Steps (iOS): confirm daily step totals are not inflated when both Apple Health and Mobile Track are enabled.
• Sleep: verify the Sleep tab shows sleep scores if historical data exists.
• Migration: if you previously failed to migrate a Fitbit account, attempt the migration flow again.

Troubleshooting steps if issues persist

• Force‑quit and relaunch the app.
• Clear the app cache (Android) or offload/reinstall the app (iOS) if corruption is suspected.
• Disconnect and reconnect third‑party integrations, starting with Health Connect connections, to force a fresh sync.
• Revoke and regrant Health permissions for Google Health and your third‑party apps.
• For Fitbit migrations, ensure the Fitbit app is updated and that the device is connected to the internet during the transfer.

When to contact support If problems continue after applying the update and following troubleshooting steps — for example, if migration repeatedly fails or major data discrepancies remain — capture screenshots and timestamps and contact Google Health support. Precise logs reduce back‑and‑forth and accelerate resolution.

Practical recommendations for users who rely on Google Health daily

1. Treat one app as the master record. If you use multiple trackers and services, choose a single one as the primary upload source to Google Health. Redundancy invites duplication.
2. Regularly export critical logs. If you need historical data for coaching, medical review or personal records, export or back up periodically.
3. Revisit goal settings after major updates. Macronutrient guidance and chart changes can make it sensible to re‑calibrate targets.
4. Use the update rollout to audit integrations. Open connected services in Health Connect and third‑party app settings; remove redundant connections.
5. Check accessibility settings. If you depend on assistive technologies, confirm VoiceOver or TalkBack improvements apply to your most used flows.

Example workflows

• Runner workflow: Configure your run watch or preferred running app to upload to one central service (for example, Strava). Let Google Health pull from that single source. After 5.01, verify run labeling, splits and GPS maps.
• Diet tracking workflow: Choose one food logging service for everyday entries. If you must use multiple services, connect only one to Health Connect and allow the other to export CSVs you then import manually to avoid duplication.
• Sleep workflow: If you track sleep via a wearable, confirm that device’s app is connected to Google Health and check sleep score consistency after the update.

What the update does not (yet) deliver

5.01 restores many things but does not deliver every requested feature. Notable limitations:

• You cannot create new custom foods within the app yet — only view and log previously created custom foods. Google says creation of new custom foods is coming in a later update.
• Cross‑platform parity remains a work in progress; small differences in unit switching, timeline behavior and UI persist.
• Deduplication and mapping improvements will reduce but might not eliminate all cases of duplicate logs; some edge cases require additional engineering to resolve.

Expect iterative improvement rather than all‑at‑once perfection. Google has published a larger roadmap of changes planned for the coming months; those future updates will likely tackle deeper integration and feature gaps.

How this fits into the broader health app ecosystem

Google Health operates in a crowded space that includes Apple Health, Fitbit, MyFitnessPal, Cronometer, Lose It, Strava and numerous device vendors. Each player has its own data model, API quirks and business priorities. The challenge for any aggregator is to stitch together consistent, accurate records when sources disagree or send duplicate information.

Health Connect is a native attempt within Android’s ecosystem to simplify that problem by acting as an intermediary. But multiple integration channels — direct APIs, Health Connect bridges, device vendor syncs — create overlapping pathways. User behavior adds complexity: people change devices, switch apps, and sometimes grant redundant permissions.

The practical result: any aggregator must constantly refine deduplication, mapping, and recovery flows. Google’s approach with 5.01 prioritizes correctness of existing records and smoother migration for Fitbit users, reflecting a recognition that reliability is a precondition for adoption.

Competitive implications

• For users who prefer tight device‑app integration and consistent data presentation across devices, Apple Health paired with an iPhone and Apple Watch still represents a cohesive option.
• Google Health’s strength lies in its ability to aggregate across Android devices, Fitbit devices, third‑party apps and Health Connect. Fixes that improve cross‑integration behavior increase its appeal to users who mix ecosystems.
• Third‑party food apps maintain their own value for detailed logging and community features, but seamless import into a central health app reduces friction for users who want a single dashboard.

Privacy and data governance: practical considerations

The update focuses on functional fixes rather than new data flows. Users should still be deliberate about permissions and data sharing. Granting access to Apple Health, Health Connect or third‑party apps means those services can view and sometimes modify records.

Practical advice

• Audit app permissions periodically. Remove access for apps you no longer use.
• For migration scenarios (Fitbit to Google), understand that the transfer consolidates historical data under your Google account; verify which data categories migrate and how they are represented.
• When troubleshooting, avoid publicly sharing screenshots that contain sensitive health information.

Developer and partner implications

Developers integrating with Google Health should note the following:

• Improved mapping logic for meal types may affect how third‑party apps present logged foods once ingested into Google Health.
• Deduplication behavior means apps that previously relied on multiple integration channels should reconsider their integration strategy to avoid unexpected suppression of legitimate entries.
• Accessibility enhancements raise the bar for partners; ensuring proper metadata and semantic labels in data payloads will maintain usability for assistive technologies.

For vendors of wearables and trackers, the update highlights the importance of unique identifiers and robust metadata. When a wearable’s associated app provides unique meal or workout IDs, deduplication becomes easier and more accurate.

What to expect next: likely priorities for upcoming updates

Google has signaled a larger list of improvements coming in the months ahead. Based on the 5.01 focus and common user feedback, anticipated next steps include:

• In‑app creation of new custom foods.
• Additional refinements to deduplication and mapping logic across more third‑party services.
• Further UI and chart parity across Android and iOS.
• Enhanced analytics and trend detection based on more reliable historical data.
• Continued accessibility refinements.

Users should expect incremental feature rollouts that prioritize reliability first and then expand on convenience features like in‑app custom food creation.

Real‑world scenarios: how 5.01 changes day‑to‑day use

Scenario 1 — The commuter counting calories A commuter who logs packed lunches in MyFitnessPal and step counts through an iPhone could see inaccurate daily breakdowns when meals were labeled “Other” and steps doubled. After updating to 5.01, their lunch entries show in the correct meal category and step totals align with expectations, making the app a useful daily check for caloric intake versus expenditure.

Scenario 2 — The weekend long run A recreational runner using a GPS watch found that several runs were misclassified and missing split details, complicating training. With the update, those runs reappear correctly labeled, splits return, and the runner can monitor pace and recovery across weeks.

Scenario 3 — The Fitbit loyalist A user who relied on a Fitbit for years wants to switch to a Google account but was blocked during migration on iOS. After the update, the migration completes and historical sleep, heart rate and activity data appear in Google Health, preserving continuity for long‑term trend analysis.

Scenario 4 — The coach monitoring athletes A coach reviewing athlete data across platforms benefits from corrected run labels and consistent nutrition charts, enabling clearer load management and dietary recommendations.

Measurements to watch after updating

• Consistency of meal types across a week: check whether Breakfast, Lunch, Dinner and Snack distribution now reflects reality.
• Step count stability on iOS users who enabled both Apple Health and Mobile Track.
• Accuracy of labeled workouts and presence of splits for runs.
• Presence and trend continuity of sleep scores.
• Speed and reliability of Friends & Family screens and the Today feed.

Monitor these metrics for a couple of update cycles. If issues recur, report them with detailed timestamps so engineers can reproduce and fix edge cases.

FAQ

Q: How do I get the Google Health 5.01 update? A: Update Google Health through the Google Play Store (Android) or the App Store (iOS). The rollout begins now and will continue over the following week; availability can vary by device and carrier.

Q: I used to create custom foods — where can I create new ones now? A: Version 5.01 allows viewing and logging of previously created custom foods but does not yet support creating new custom foods within the app. Google has stated in release notes that creation will arrive in a future update.

Q: My run previously appeared as the wrong activity type. Will 5.01 fix historical entries? A: Yes. Google’s update corrects mislabeled runs and restores split data for affected run summaries so both new and historical runs should display properly.

Q: I saw duplicate step counts on iOS. Does this update fix that? A: 5.01 resolves the issue where some users saw double counting when both Apple Health and Mobile Track were enabled. After updating, verify your step totals and consider disabling redundant sources if any duplication persists.

Q: I attempted Fitbit-to‑Google migration on iOS and it failed. What should I do? A: Update to 5.01 and attempt the migration flow again. Google indicates that restarting the migration will allow the move to a Google account. If problems persist, ensure both the Fitbit and Google Health apps are up to date, try on a different network, and contact support with screenshots.

Q: Will my unnamed food logs be readable after the update? A: Yes. The update assigns default names to unnamed food entries imported through Apple Health so they become identifiable in the timeline.

Q: I use multiple third‑party food apps. How can I avoid duplicate logs? A: Connect only one source to Google Health through Health Connect or direct integration to serve as the master. If you need multiple services, disconnect redundant connections or export/import logs manually to avoid duplication. After 5.01, Google has improved deduplication when the same meal arrives via multiple channels, but edge cases remain.

Q: What should I do if maps still won’t load for GPS workouts? A: First, confirm location permissions are granted and the app has access to the device’s location. Force‑quit and relaunch the app, and verify the watch or phone uploaded GPS data. If maps still fail to load after these steps, clear the app cache (Android) or reinstall (iOS), and contact support with details.

Q: Are there accessibility improvements in this update? A: Yes. The update enhances VoiceOver (iOS) and TalkBack (Android) support by improving buttons and chart labels to improve navigation for users who rely on screen readers.

Q: Does this update change how my health data is stored or shared? A: The update focuses on functionality and fixes. It does not introduce new, publicly announced changes to core storage or sharing models. Users should continue to review permissions and account settings and back up important data prior to major changes like account migrations.

Q: What remains missing or incomplete after 5.01? A: Primary limitations include the inability to create new custom foods within the app and the possibility that some rare deduplication or mapping edge cases will persist. Google plans additional improvements over the coming months.

Q: Who should I contact if I find persistent issues after updating? A: Use Google Health’s in‑app support or the official help center to report issues. Include device model, OS version, app version, timestamps and screenshots to expedite resolution.

Q: Will changes to nutrition and activity charts affect exported or shared reports? A: Chart presentation has been made more consistent across views. Exported raw data should remain the same; charts and summaries may appear differently as Google standardizes visualizations.

Q: How often will Google Health receive updates going forward? A: Google has indicated a roadmap of changes slated for the coming months. Expect incremental updates focused on reliability, feature parity and new capabilities like in‑app custom food creation.

Q: Should I reconfigure my connected services after installing the update? A: It is prudent to review connected services. If you previously experienced duplicates or mapping errors, disconnect redundant connections and reconnect a single source where possible to ensure clean, reliable syncing.

Q: Will this update benefit users outside the U.S.? A: The fixes target functional behavior that applies globally. However, rollout timing can vary by region and carrier. Users should check their app store for availability and follow the verification checklist after updating.

This update prioritizes fixing the small but consequential errors that undermine a health app’s usefulness. Whether you track meals to manage weight, runs to prepare for a race, or sleep for recovery, the improvements in 5.01 make Google Health a more reliable daily tool. Apply the update, verify the critical flows you depend on, and follow the practical steps listed here to keep your data clean and trustworthy.