Google pushed out version 5.04 of its Health app this week, restoring the ability to log meals with previously saved custom foods and introducing a Quick Logging option for rapid calorie and macronutrient estimates. The update, rolling out to Android and iOS, fixes multiple nutrition-tracking gaps that have frustrated Fitbit users since Google overhauled the health platform.
Nutrition Tracking Gets a Concrete Repair
The release notes on Google Play list the marquee changes clearly: users can once again “view and log previous custom foods,” and the app now handles food logs from multiple sources more gracefully. Behind those bullet points sits an important correction. When Google launched its new Health app, many Fitbit migrants discovered that custom foods—personalized entries for recipes, meal preps, or niche ingredients—had vanished. Version 5.04 is the first release that begins to bring them back.
Details from Android Central suggest the fix may go further than the Play Store notes let on. According to their reporting, the update lets users “create, edit, and delete” custom foods, and includes a search function to surface older entries. Google itself has not confirmed full create-and-edit privileges in writing, but a June post by a community specialist acknowledged the team was “rebuilding the feature for a later release.” Users should treat the app store wording as the official feature set until Google directly updates its support documentation, and test whether full editing is live for their account before relying on it for daily logging.
Alongside the custom foods fix, Google added a Quick Logging mode. This lets you bypass the food database entirely and punch in calorie, protein, carbohydrate, and fat numbers directly. Anyone who cooks at home, subscribes to a meal kit, or eats at chain restaurants with published nutrition labels will find this far faster than hunting for a matching database entry that may not reflect actual portion sizes.
The rest of the update tidies up ongoing rough edges. Macronutrient percentage calculations have been corrected—a fix that should give a truer picture of daily macro splits. Cycle Health views now display trends in chronological order, designed for long-term analysis. Naps finally appear on the Today tab, so short rest periods won’t distort overnight sleep metrics. On iOS, incomplete heart-rate charts and exercise maps that failed to represent full workout durations have been repaired, and friend invitations now work properly.
| Feature | Change in v5.04 |
|---|---|
| Custom Foods | View, log, and (per Android Central) create, edit, delete previous custom foods |
| Quick Logging | Enter calorie and macro estimates directly without searching for a food |
| Macronutrient % | Calculation bug fixed |
| Cycle Trends | Switched to chronological order |
| Naps | Now shown on the Today tab |
| iOS Exercises | Heart-rate charts and maps reflect full workout duration |
| iOS Friends | Friend invitations re-enabled |
| Multi-source Logging | Improved handling of food data from different apps and devices |
What This Means for You
For anyone tracking daily nutrition: If you abandoned Google Health because a favorite home-cooked chili or protein smoothie disappeared from the database, this update gives a reason to check back. Previously saved custom foods should be searchable again, and you may be able to add new ones immediately, depending on the rollout. The Quick Logging tool is a practical addition for meals where a precise database match never existed. Open the app, tap the Quick Log option (if it appears), and plug in the totals from a restaurant’s nutrition facts page or a recipe calculator.
For Fitbit power users: This is the first concrete step toward restoring parity with the old Fitbit dashboard. If you have years of custom food history, updating to v5.04 will reveal whether those entries survived the migration. Hold off on deleting any records or switching platforms until you’ve confirmed they appear. If full create/edit isn’t yet available on your account, the community specialist’s statement suggests it is on the way.
For iOS users specifically: The exercise heart-rate chart and map fixes matter most. Previously, a 45-minute run might have shown data for only the first 20 minutes. Version 5.04 should now display the full session. Friend invitations, broken for some, should also work again, so you can return to competing on leaderboards.
For Windows users: Google Health remains mobile‑first. There is no native Windows app, and the web dashboard at health.google.com offers only a limited view of data. That said, if you use a Fitbit device alongside a Windows PC for work, the improved logging means your food diary will be more accurate when you review trends on a larger screen. It also means less frustration when you quickly add a meal after lunch before getting back to your desktop.
How We Got Here
Google’s rebranded Health app launched with a clean interface and deep Fitbit integration, but it stripped away several features that long‑time users considered table stakes. Custom foods, a staple for anyone tracking home‑cooked meals, were cut. The June response from a Google Health community specialist confirmed the feature was not supported in the preview app and that the team was “rebuilding” it. Meanwhile, version 5.03 arrived a week earlier and focused on health metrics, adding tiles for heart‑rate variability, oxygen saturation, skin temperature, blood glucose, and more, setting the stage for the nutrition overhaul that followed.
The gap between what Android Central reports and what the official Play Store notes list is not unusual for staged rollouts. Google often activates features server-side, so some users may see full custom food creation while others only see the ability to view and log old entries. The inconsistency underscores how Google Health is still a work in progress, with features reappearing patch by patch.
What to Do Now
Open the Play Store or App Store on your device and update Google Health to version 5.04. If the update isn’t yet available, check back over the next few days; staged rollouts can take a week or more to reach all regions.
Once updated:
- Search for an old custom food from your history. Tap the food logging section, use the search bar, and look for entries you created before the migration. If they appear, you’re on a build that restores saved custom foods.
- Try creating a new custom food. If the option to “create” or “add custom food” is present, full editing is live for you. If not, check again later; Google may enable it without an app update.
- Test Quick Logging. When logging a meal, look for a “Quick Add” or “Quick Log” button. Enter rough calorie and macro numbers and verify they appear in your daily summary.
- Review macronutrient percentages. After logging a few meals, check whether the pie chart or macro breakdown now matches your actual intake. If you spot a discrepancy, force‑close and reopen the app, then recheck.
- On iOS, confirm that a full workout’s heart‑rate chart displays all data points and that the exercise map shows the complete route. Try inviting a friend via the app to confirm the invite flow works.
If custom foods still don’t work or Quick Logging is missing, wait for a further update. Google’s community statements and the staged rollout suggest these features will reach all users within weeks.
What to Watch Next
Nutrition logging will remain a focus for Google Health. The Quick Logging addition hints at a design philosophy that values speed and flexibility over rigid database lookups. Future updates may add photo‑based logging, barcode scanning that syncs with custom databases, or tighter integration with Google’s AI tools to estimate meal contents from a simple description. Android Central’s report frames version 5.04 as “the main course,” implying that Google still has dessert and sides on the roadmap.
For now, the returning features should make daily tracking less of a chore. The patchwork nature of the rollout means patience is required, but the direction is clear: Google is listening to a vocal base of users who felt abandoned by the platform reset. The next few versions will reveal whether the rebuild delivers the full freight of Fitbit-era tools or sticks to a simplified modern approach.