Google Health 5.08 is now rolling out on Android devices and is fully available on iOS, marking the smallest update since the May redesign. The release forces users to sign in with a Google Account, removes any Fitbit data that was not migrated, and resolves a lingering sign‑up issue for email addresses previously linked to Fitbit.
Key Takeaways
- Google Health 5.08 is the smallest update since the May redesign.
- The update is rolling out on Android and is already live on iOS.
- A Google Account is now mandatory for app access.
- Unmigrated Fitbit data is being deleted as Fitbit logins are no longer supported.
- General stability improvements and a fix for a sign‑up glitch are included.
| Metric | Value | Why it matters |
|---|---|---|
| Version | 5.08 | Indicates the latest iteration after a series of incremental upgrades. |
| Platforms | Android (rolling), iOS (full) | Ensures both major mobile ecosystems receive the changes. |
| Account requirement | Google Account mandatory | Consolidates user identity under Google’s ecosystem. |
| Fitbit data handling | Unmigrated data deleted | Closes the migration window and removes legacy login paths. |
What’s new in Google Health 5.08
The update focuses on three core areas: authentication, data hygiene, and reliability. By making a Google Account the sole gateway, Google eliminates the need for the now‑defunct Fitbit login flow. The system also purges any Fitbit data that failed to migrate before the cutoff, ensuring the backend only stores active, linked records. Finally, a batch of stability patches addresses crashes and UI glitches reported after earlier releases.
Account changes and the end of Fitbit logins
Users who previously accessed Google Health through a Fitbit account will find that those credentials are no longer accepted. The migration period has closed, and the app now enforces a Google Account login for all functions. This shift aligns the health platform with Google’s broader identity strategy and simplifies the authentication stack for developers.
Data cleanup: Deleting unmigrated Fitbit information
Any health metrics, activity logs, or personal settings that remained tied to a Fitbit account after the migration deadline are automatically removed. The deletion is a direct consequence of the statement that “Fitbit account logins are no longer supported,” and it prevents orphaned data from lingering in Google’s servers.
Stability improvements and bug fixes
Beyond the account overhaul, Google Health 5.08 bundles general stability enhancements. While the source does not enumerate specific bugs, the language “general stability improvements and bug fixes” signals that the release addresses a range of low‑level issues that could affect performance, battery consumption, or UI responsiveness.
Recent rollout history and what’s next
The 5.08 release follows a rapid cadence of updates. Version 5.07 introduced better manual logging, enhanced map visualizations, and additional features, while 5.06 gave users control over the Health Coach widget on the Today tab. Google has already tackled most items on its post‑redesign roadmap, leaving the Health Coach as the primary focus for upcoming work. Rumors of a Wear OS‑powered fitness tracker filed with the FCC hint at possible hardware integration down the line.
Why it matters
Requiring a Google Account consolidates user data under a single identity, which can improve cross‑service personalization but also raises privacy considerations for users accustomed to the Fitbit login. The forced deletion of unmigrated Fitbit data cleans the backend but may surprise users who expected legacy data to persist. Finally, the stability patches help maintain a smooth experience as Google continues to iterate on the health ecosystem, positioning the app for future features like an integrated Wear OS tracker.
Frequently asked questions
What is Google Health 5.08?
It is the latest version of Google’s health‑tracking app, released as the smallest update since the major redesign in May.
Which devices receive the update?
The update is currently rolling out to Android smartphones and tablets, while iOS devices already have full access.
Do I need a Google Account to use the app now?
Yes. Access to Google Health now requires signing in with a Google Account; Fitbit logins are no longer accepted.
What happened to my Fitbit data?
Any Fitbit data that was not migrated before the cutoff is being deleted, as the app no longer supports Fitbit account logins.
When will Android users see the update?
The rollout is ongoing on Android as of today, with devices receiving the update gradually.
Bottom Line
Google Health 5.08 streamlines authentication by mandating a Google Account, cleans up leftover Fitbit data, and delivers a set of stability fixes, all within the smallest patch since the May redesign. Android users should expect the rollout to finish soon, while iOS users already have full access.
Reporting based on: original source.
Comments
Post a Comment