Google Health app 5.04: custom foods, nap tracking and cycle history get an upgrade

Google has started rolling out version 5.04 of the Google Health app for both Android and iOS. The update began shipping in early July 2026 and will reach users in phases over the following week, depending on carrier and device.

The release follows three previous updates in the 5.x series and touches several core areas of the app: nutrition logging, sleep tracking, exercise summaries, cycle health, and social features. None of the changes are dramatic on their own, but together they address real pain points that users have raised in the community forums.

The rollout also arrives against a backdrop of user frustration. Many people who use Fitbit devices alongside Google Health have been reporting sync and tracking issues, and the community forum for this update is full of complaints about those problems sitting unresolved while new features ship.

What's new?

Here's a full breakdown of what version 5.04 adds and fixes:

• Custom foods: You can now create, edit, and delete your own food entries. Once created, they're searchable and can be logged again without re-entering the details.
• Quick calorie logging: You can log a meal by entering just calories and macronutrients, without searching for or naming a specific food. Useful for rough estimates.
• Macronutrient percentage fix: A bug that caused incorrect macronutrient percentages for some users has been corrected.
• Naps on the Today tab: Nap duration now counts toward your total sleep figure shown on the Today screen.
• Exercise summary fix: Heart rate charts and maps in exercise summaries were sometimes cut short, not showing the full workout. That's now fixed.
• Cycle history by year: You can now view your full cycle history grouped by year, making it easier to spot long-term patterns.
• Friend requests on iOS: A bug that stopped some iOS users from sending new friend requests has been resolved.

Why does it matter?

The custom foods feature is probably the most meaningful addition here. Nutrition logging apps live or die on how easy they make data entry. If your go-to breakfast isn't in the database, or you want to log something you make at home, having to work around a fixed food library is genuinely annoying. Custom entries fix that.

The quick calorie logging option is a smart addition too. Not everyone wants to track every gram of protein from a named food source. Sometimes you just want to log a rough estimate and move on. Giving users that flexibility lowers the barrier to consistent logging, which is ultimately what determines whether people stick with a nutrition tracker.

The nap tracking improvement is a smaller but welcome fix. Google has been building out its sleep features in recent updates, and having nap time actually count toward your daily total makes the Today tab more accurate and useful.

The context

Google Health has been going through a significant transition over the past couple of years, absorbing features and users from Fitbit after Google's acquisition of the company. That process has not been entirely smooth. Users in the 5.04 community thread are openly frustrated that Fitbit device integration is still broken for many people, including those whose Fitbit Aria Air scales stopped syncing with the app.

The complaints point to a broader tension in how Google is managing the transition. Several users noted that Google's own status pages showed no issues during a period when large numbers of people couldn't use their devices properly. That kind of communication gap erodes trust, especially in a health app where people depend on accurate data.

There are also feature gaps users want addressed:

• Strava activity sync, which still isn't available
• Micronutrient tracking (fiber, vitamins, minerals) in custom foods
• Turkish language support
• Step counting accuracy, particularly for dominant-wrist users

Google says more updates are coming in the weeks ahead. Whether those updates address the deeper integration problems, or continue adding new features while legacy issues sit open, will tell users a lot about where the app's priorities actually lie.