Google Fixes Fitbit Calorie Goals; Pixel Watch Error Workaround

Google has confirmed that a fix is rolling out for an issue that caused Fitbit calorie goals to display incorrectly, and there are signs that related tracking errors on Pixel Watch devices — such as doubled step counts and other inflated metrics — are also resolving for many users. If you continue to see incorrect numbers, there are a few troubleshooting steps that may help while fixes complete their global rollout.

The Fitbit app tracks more than steps and heart rate: it helps log food and provides personalized calorie targets to guide daily intake. Over the past couple of weeks, some users reported that the app showed inaccurate calorie goals or left the “calories left” field blank. Google says the underlying cause has been identified and a remedy is now being distributed to affected accounts.

A Fitbit community moderator identified only as “Mario S” posted that the team found the root cause and is implementing a fix. The moderator indicated that corrected personalized calorie goals should begin appearing properly and that the full rollout should reach all users within a few days.

…Our team found the cause of the issue and are currently fixing it.

Personalized calorie goals should now be showing up correctly. Please note that if you manually set a fixed goal as a temporary workaround, that fixed goal will remain until you change it.

You might still see an error message when creating or updating a food plan, but we expect to have this resolved within the next few days.

While the calorie-goal problem has a targeted fix, some Pixel Watch owners have also reported recent discrepancies in Fitbit metrics after a device update. Reports include doubled step counts, unusually high calorie burn numbers, and inflated cardio load readings that do not match actual activity. For example, users have noted cardio goals exceeded by large percentages despite limited movement during the week. The exact root cause of those errors is still unclear, but many users are seeing their stats return to normal as fixes and updates propagate.

If you are still experiencing doubled steps or erratic metrics on a Pixel Watch, a few simple actions have helped others get accurate readings again. Rebooting the watch has corrected counts for some users. A drained or replaced battery — which forces a full restart — has also coincided with a return to normal values for certain owners. In other cases, clearing the Fitbit app cache on the connected phone has removed duplicate or stale data and stopped the double-counting behaviors temporarily.

To summarize practical steps you can try if you see incorrect Fitbit data:

Restart your Pixel Watch and let it reconnect to your phone.
If possible, allow the watch battery to fully drain and then charge it back up, which forces a full reboot cycle.
Clear the Fitbit app cache on your phone to remove any corrupted or outdated local data; afterward, sign back into the app and allow it to resync.
Check the Fitbit app settings to confirm whether you switched to a manual, fixed calorie goal as a temporary workaround; if so, revert to personalized goals once the service reports the fix.

These steps are practical stopgaps while Google and Fitbit finish rolling out server-side corrections and any necessary app updates. If issues persist after attempting these measures, the Fitbit community forums and official support channels remain the best places to report ongoing problems and receive tailored guidance for your device and account.

If you’ve already seen your metrics return to normal, it’s likely the fixes have reached your account. If not, trying the steps above often resolves the issue quickly, and broader updates should continue to improve stability over the coming days.

Let us know in the comments below if you’re still seeing problems with calorie goals, step counts, or other Fitbit stats so other readers can compare notes and share what worked for them.

More on Fitbit: