Calories burned in app much higher than on watch, updating retroactively

[dnandrei]

App version: 4.24 (Android)
Device: Pixel 9 Pro XL
Watch: Pixel Watch 2

Beginning yesterday (Sep 2) I noticed a discrepancy between the number of calories burned shown on the watch and the number of calories burned in the app. About 400cal or so. I thought the problem would solve itself once a new day begins, but it doesn't seem to be the case.

Today my watch is showing at this time 2,882cal, while the app is at 3,282cal (both values current and refreshed).

Under Energy burned I started looking back at the previous days, as well as the previous weeks, and as I moved through each day, the calorie count was revised upwards on each day / week I scrolled through by quite a lot (so calories per day went up, averages per week went up as well). I switched to the month view, and it did the same when I went back a few months more. Now I'm afraid I've destroyed several months worth of calorie data.

I'm seeing other people report similar calorie burn issues. What's happening?

Edit: I have tried clearing storage / cache on the app, basically starting afresh (logging back into my account and all). This has not fixed the issue, and historical data is still affected. I would have liked to compare data from the app to the dashboard on the website, but I was unpleasantly surprised to realize you have further enhanced my premium experience by removing it. Just great..

[SampleRuns]

Okay, so this is happening to me as well. Starting the other day. My app on my phone is preemptively calculating my calories burned for the rest of the week, before it's happened. 

The numbers on my watch and my app are different (app is higher) even though I have synced them and tried logging out etc. 

I have no idea what is accurate anymore and I'm thinking it's time to change to Garmin or another tracker. 

[dnandrei]

In my case the calories recorded in the app are pretty consistently 1.14x the calories on the watch (2,669 in the app, 2,343 on the watch). This was true at all times during today and yesterday, when I started keeping an eye on it. Why 1.14 (well, 1.14 +/- 0.001 to be very specific)? No idea.

[dnandrei]

The problem appeared fixed last night and this morning, however is now back. Ah well..

[SampleRuns]

Ugh, I see that. That's incredibly disappointing. Hopefully it it's a problem for enough people, they'll actually fix it.. 

Beyond frustrated 

[RiekoC]

Hello @dnandrei & @SampleRuns 

There is an issue with calorie tracking. The issue has been escalated and, as far as I know, the team is working on a fix.

That said, I've seen some users report today (06 Sep 2024) that their calorie tracking is back to working properly.

Please let us know if you are still seeing an issue with calorie tracking.

[dnandrei]

Yes, it's still happening. Two days ago it was fine for some time (evening in Europe), but then by morning it was messed up again. Since then it has consistently been wrong (I've tried once more now, just in case).

Is anyone actually doing any kind of QA testing before releasing things? You know, manual testing, exploratory, running automation tests, unit tests, that kind of stuff. This is blatant, it's not something that should reach production, it's too visible, anyone testing should have seen it. Wtf...

[ndoty87]

I noticed this the other day and it's a bit irritating. It doesn't seem accurate and is throwing off my My Fitness Pal.

[SampleRuns]

Yes this issue is still happening. It was fixed for a few hours one evening, and has gone back to being incorrect.

[dnandrei]

4.25 came out, and the problem is still present. To me it looks like a server side issue (especially since it had been corrected briefly at the beginning of the week).

When is this going to be fixed? It's already been a week, and this is making the app semi-useless.

[dnandrei]

Bump, because I'm sick of Fitbit messing this up and then going full radio silence, especially when paying for Premium. It's been 10 days, and the calories are still messed up. Anyone there? Support? Does anyone at Fitbit care? Echo..? echo... echo...

[dnandrei]

O look, new version! But does it solve the problem? No, of course it doesn't... Wtf

[Lazydog11]

Same issue. Calories burned are around 800 to 1000 higher than actual. Plus it also shows 1300 calories burned per day for the next 3 days. Been wrong for a long time now, initial word on these forums was they would have a fix by 10th September, but that's obviously not happened. Would be nice to have some sort of statement from them to let us know what's up.

[SampleRuns]

Yep, I received an email from tech support asking if I was happy with the resolution. I was like what resolution?? It was fixed for 3 hours then went back to being broken? Haven't heard any updates since. 

Definitely time to start looking at other apps/devices for me

[dnandrei]

Bump. Because I find it annoying that two weeks later this is still happening, and there has been no official communication about it. This is totally disrespectful towards the community as well as to users who pay for this crap.

[gwinness]

This is happening to my tracker as of today.

[dnandrei]

Bump, because it's been more than a month, and apart from being acknowledged and the team 'working on a fix' since forever, nothing has changed. This is ridiculous, especially when paying for premium. It's also a server side issue, demonstrated by the issue temporarily being fixed for a few hours a month ago. I get the feeling that this app is really a mess, and I am starting to give up hope at this point. To be frank this is happening more and more when it comes to most Google products, but I digress.

[dnandrei]

Bump, because no one bloody cares. A fix was promised, it was allegedly being worked on. Almost two months later and still no one cares. There is no timeline, no updates, the issue is still present.

But they expect people to pay for premium on the other hand...

[FEDO80]

This has been happening to me too. I reported it to fitbit a while back. Nothing was done. 

[dnandrei]

Same. Fitbit support I've talked more than a month ago to claimed they knew about the issue and that they're working on a fix. They never fixed anything (the fix would be on the backend, not the app itself anyway). I have cancelled my Fitbit Premium moving forward.