Android Fitbit app not tracking food and calories intake

[Stevie2625]

I've had an issue for a few months now where my logged food doesnt accurately show up on the main screen icon, and instead have to open the full food log to view my calories.

Starting yesterday, the food log is not displaying my calories at all after adding them. Hours later, they might show up, along with all my other attempts to log my food. It's been a mess, and I've had to resort to just writing it all down.

Customer Support told me to log out, restart my phone, log back in, and try logging. That didn't work. Then they said to uninstall the app and reinstall the app. That didn't work either. I'm still having this issue today, and it's quite frustrating because it's like the main thing I use this app for.

Is this some bug that just needs addressed in an update? My app is up to date, having an update done two days ago. Anyone else having this issue? 

Edit: I would like to add that this only seems to affect the quick calories input. Any specific measured food I add seems to show right up, but since I use quick calories throughout most of the day, I cant accurately track my food anymore.

Moderator Edit: Clarified subject

[brownawella]

No as I have had 3.59.1 on Android since March

[seraphim49]

No, I don't believe so.  I have had 3.60 (20263717). on my Android since June 14th.  Sadly it worked for a few days and then the app became worse than ever before.

[Smstext]

Support told me a month ago that 3.6 for Android was being released to fix
the issues, however a forum beta tester said the beta version didn't cover
any of the issues and was only fixing minor bugs, just confused as no one
seems to know what's going on, would love someone from Fitbit to please
come on here, see the issues and give us all an ETA or the issues being
resolved. Not asking for the world but some customer relations exercise as
I see to many people are losing their patience.

[Sheshesh]

I asked Support to pass along a request to the department that is working on this bug to perhaps pin an update to this thread ( if possible) and keep us in the loop. First time I asked, chat abruptly ended (0.o). Second time, the Rep seemed honestly concerned an said he/she would pass the request along. We'll see...

[aelo]

For me, now it's the sodium count which has been so wildly off since mid-May. I've had weeks of 6,000+ mg. sodium days according to the Fitbit app. I think I would have had a stroke by now if the Fitbit app was accurate. I use the MyPlate app now to keep an accurate count now. Maybe Google/Fitbit should contract with MyPlate's programmers. Both apps seem to use the same nutrition values database.

[SunsetRunner]

Thanks for the tip!

[LizzyFitbit]

Hi everyone.

Thanks for keeping me posted about this situation. I understand where you're coming from about not being able to use the Food tile as before. As mentioned before, our team is aware of this situation and they're working hard to bring a permanent fix to all our affected members. I apologize for this inconvenience and appreciate your feedback. 

While I don't have a time frame or more details to share, we'll keep providing your comments to our team so they can be informed of the impact to all our members. As soon as I have more information, I'll update this thread.

As a friendly reminder, we want our Fitbit Community to be a place where users can come to share their feedback and stories in a conducive manner, so please keep in mind the Community Guidelines when posting.

[SpinnyMin]

A couple of days ago I updated the firmware. 

Food tile has since been working as it should. Hopefully it will stay this way. 

Now running 36.128.6.12 on Huawei P30 pro, EMUI 12.

[Super8]

Thank you for responding however the food tile has been an issue since before 3.591 release. That's a lot of time to expect users to be "patient" and remain customers. Is there a ballpark timeline at least?

[TripleDeuce222]

To Fitbit:

I don't know if the following details help or not, but I decided on a whim to try it out on another of my devices. To my surprise it actually worked on my tablet (although since I can't keep it with me all the time, it doesn't make for a great solution). Anyway, take this for it's worth, as I've seen many people report that it can work for a while, and then suddenly stops working. Here are my device details which may or may not be relevant:

Food tracking IS NOT working on the following device:
Samsung Galaxy S21 Ultra (SM-G998U)

Fitbit Version: 3.59.1

One UI Version: 4.1

Android Version: 12
Google Play system update: May 1, 2022

Android security patch level: May 1, 2022

Food tracking IS currently working on the following device:

Samsung Galaxy Tab S7+ (SM-T970)

Fitbit Version: 3.59.1

One UI Version: 4.1

Android Version: 12
Google Play system update: April 1, 2022

Android security patch level: June 1, 2022

What I observed is that the Google Play system update and the Android security patch level are different between the two devices. This may or may not be relevant to the problem at hand, but thought I'd share just in case.

[OldGuy51]

It is a pain in the backside to track what you eat any given day but when an app doesn't retain what you log that adds a new level of frustration. I started using the Fitbit food logging feature of the android phone app about a week ago with the data being synced to Fitbit.com. The syncing stopped three days ago. I lost the data for the last three days when I did a force stop of the app on my phone. App version 3.59.1 

  Any one else experiencing this app behavior?

Update 6/24: The website food log entries eventually appear in the android app. The android food log entries are not appearing in the website. Prior to 6/21, android app food log entries synced to the website. Something changed on 6/20 or 6/21.

[SC_DEBBY]

Do you have a time frame on when this will be fixed?

[infin0]

It's random, sometimes it works and sometimes not. 

[CJHillyard]

I've been experiencing the same thing and as of today I canceled my premium subscription because the problems have been going on far to long and not worth the premium membership fees no matter how much I enjoyed them while I was able to use them. I'm sure if Fitbit made the corrections to the issues many more would be keeping our memberships, services and trackers. But now I'm actually considering returning my Chrage 5 and restarting with another. Such a shame

[SunsetRunner]

It's still not working and I'm getting ready to delete the app and ditch the device. What's the point of paying for a thing that doesn't work for months or weeks at a time? I'm super frustrated. 

[ccddff]

Same!!!!

[Don34]

I was having an issue with the barcode scanning to my food list sometime back.  It seemed the suggested fix was to delete the app and reinstall.   I did and it worked. 

Today having the same problem.  Tried the same fix and it comes back up with all the calorie data missing since the 18th, even what I had logged for lunch and breakfast today.

Was really starting to rely on this app after Nutrisystems let us down. 

Any ideas?  Tech support doesn't have any.

[DelBoy55]

I'm getting the same issue using Fitbit Android version 3.59.1 (20263715) on a Samsung Galaxy S21 5G. I can log food on the app and it appears to work alright on the day, but the following day the food is still in the log but the graph is showing no calorie intake:

It's not even working properly using the online account dashboard.

Also, when I now save a custom food it doesn't save properly. For example, if I save a food with 100 grams unit and 600 calories per unit, it works OK first time but if I log the food the next day it says unit is 1 bar with calories 600 and changing to say 0.38 for 38 grams the calories stay as 600.

This has been happening for about a month now so can the Fitbit support engineers please sort this out.

I am on the premium trial as it is a new Fitbit Inspire 2 but have now had a month of not working correctly, so will Fitbit extend my trial period to compensate?

[GingerLu]

Thank you for the update LizzyFitbit.

Question- I heard that this issue might be due to using older generation Android devices. I am planning on upgrading to a new-to-me phone. Do you know if upgrading to a newer Android would fix the issue?

[laross]

I doubt it.  I have a 5G phone -- Galaxy S20 FE 5G. Android version 12.  The latest Android update might have messed things up.  May 22 update seemed to start problems for me.