Fitbit users got a nasty surprise this week when their carefully logged meals started vanishing into thin air. What began as scattered complaints quickly turned into a flood of frustrated reports across both Android and iOS platforms.
The official Fitbit community forums lit up with users describing a maddening pattern: they would log a meal, watch it appear for a few seconds, then see it disappear completely. One user noted that their morning snack and lunch entries vanished, leaving only breakfast behind.
Others described an almost comical scenario where logging lunch would delete breakfast, and re-logging breakfast would wipe out lunch. “It’s been like an old school video game for me. Space Invaders, arcade version, but with food,” one user joked.
Fitbit has acknowledged the problem on its official status page, confirming that food logging is currently unavailable.
A moderator reached out to affected users on the community forums, asking for specific details to help with the investigation. The team wants to know whether the bug affects the plus sign in the dashboard or the food section directly, whether it hits all meals or just certain ones, and whether custom foods or database entries are impacted.
Over on Reddit, the Fitbit community saw one thread rack up well over a hundred comments from annoyed users. Many tried the usual troubleshooting steps: clearing cache, force stopping the app, logging out and back in, even completely reinstalling. Nothing worked.
This isn’t the first hiccup for Fitbit’s food tracking feature lately. Users pointed out that the entire food database disappeared just a month ago. Some frustrated users questioned whether Google, which owns Fitbit, is putting enough resources into keeping the platform running smoothly.
For those who depend on calorie tracking as part of their fitness routine, the outage stings. Several users mentioned switching temporarily to alternatives like MyFitnessPal or jotting down notes manually until things get sorted.
Fitbit says they’re actively working on a fix, though no timeline has been shared.


