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

[Mrbean]

Why when I add food on either my App (Android) or on the web they don't sync? I look on the web and the food I logged in the app arent showing and visa versa.

[SunsetRunner]

So, I finally got it working on my Samsung Z Fold (I don't think the phone type, version or any of that has anything to do with it) I went to created foods to log something, I and I noticed about 80% of my created foods had been removed. I removed all the remaining 10 foods I'd created and then viola the whole thing synced up and worked fine. Now I just need to add back in any created foods, (one's that haven't been permanently added to the data base) That seems like a real hassle so I guess I'll just to that one by one as they come up. 

-----------

well, it appears I spoke to soon because all the things that appeared to be logged after deleting my created foods on the website (downloaded from the phone app) are not there this A.M. Nothing for the last few weeks. Although now the phone App is recording correctly. I'm over it. I've been wanting to chuck my fitbit and see how I do w/out it and just count total carbs anyhow, maybe now's the time to find an app that does just that. 

[Stoptravis]

Someone earlier recommended my fitness pal so I've been giving that a try. It takes a while to get used to for custom foods however... it actually logs them. For the last couple of days I've been using the Fitbit app only for tracking sleep and HR. Kind of a pain for 2 apps when 1 app used to do it all but I think it's more convenient than paper and pencil. 

[Animator]

Since June 17 the tracking has been 0. I assumed there was a problem backing up. But yesterday the Today tracking was there in the phone app. Today, yesterday tracking it's gone back to 0. And I can only see today's. 

Please fix this, extremely annoying and renders the fitbit practically useless. 

[2Cans]

Strangely my android  cell phone (moto g stylus running Android 11)  registers the items I add inside the app but not on the TODAY screen  nor on the full desktop app.  Y'all seem to think I've eaten nothing at all today and that is simply not the case. I've tried 1) restarting my phone 2) uninstalling and reinstalling the Fitbit app 3) THEN restarting my phone 4) logging out and then back in and restarting my phone all over again. It's very frustrating and I need this kind of help right now as I work on knowing what I eat and how that balances with how I move.  HELP!

[Don34]

Two days in a row I have logged out and then logged back in only to find that he days mesls that had been previously entered are now gone..

[Don34]

I'm a longtime Fitbit user.  I only recently started using the food portion and it worked great.  It worked so well that my wife ordered a Fitbit so she could use it as well.  As of this afternoon,  almost nothing works on the food portion of the app.  A few days ago upon re-installing the app it wiped out my whole last week of data.  Today I logged out and logged back in and lost the last two days.  May have to cancel that new order.

[Crawdaddii]

The fitbit app is not calculating the macros correctly. The app is miscalculating the totals when clicking Nutrition. The app says I consumed 247 grams of protein. The carbs and fat are inaccurate also. Will fitbit be pushing an update to fix this.

[Sheshesh]

There have been two updates to fix this... 3.60 and 3.62.  Neither has fixed it for me (android)

[LizzyFitbit]

Hi everyone.

Thanks for the details provided and your efforts in keeping the Fitbit app updated. Our team continues working on this situation to bring a fix to all our affected members as soon as possible. While currently I don't have a specific time frame for the fix, I'll update this thread as soon as I have information from them.

I apologize for the inconvenience this has caused, and appreciate your feedback. Please know every comment hasn't gone unnoticed as has been passed along.

[SpaceRacer]

Hi Don, I'm having the same problem along with many people in the form. It appears to be an issue with the rollout of the 3.6.0 update. Apparently that update is not available for many Android users via the Google play store. I'm on Android 12 and it's not available for me either. I have seen some people say that going to the Fitbit website instead of the app will allow you to log your meals, however I have not done it.

I'm actually about to try it now.

Best of luck. I hope there is a fix soon.

[infin0]

I can enter food by the summary screen is all funked up. 

 

[Don34]

Thank you for your reply. One of the things with "social media" is tgat
many times you don't get any kind of response unless you say something
controversial.

I visited with tech support by phone and they didn't say anything about new
firmware. They did send me am email that she ssid would explain
everything and help me fix it but it had a corrupted URL and was of no
use. Frustrating.

I don't see anything that will let me download a newer version.

When I deleted the app and re-installed it, that's when I started losing my
data.

I'm a long time Fitbit user and was hoping they'd have an answer.

Again, thanks for contacting me.

Moderator Edit: Personal info removed

[SpaceRacer]

No problem. I'm not a Fitbit employee, just a fellow user with the same issue.

I did try logging my food via the website and it does sync to the app.

It's not as convenient as just using the phone, but it works for now until Fitbit can figure out the update.

All the best.

-SpaceRacer

[MichaelBoehnke]

Hello all,

I've performed a technical analysis by capturing the network traffic of Android app version 3.59.1 (I can provide a collection of http requests if required). It turns out that the backend has (among many other endpoints) two endpoints which the app uses for logging food/creating custom food:

log food: POST https://android-cdn-api.fitbit.com/1.1/user/-/foods/log.json
create custom food: POST https://android-cdn-api.fitbit.com/1.1/foods.json

When the backend answers with the status code 201 then everything is fine and the food has been logged in the backend, i. e. it is visible in the dashboard in your browser.

On a freshly installed app 3.59.1 when I log a known food out of the database, everything is fine (status code 201). When I then add quick calories, everything is still fine (status code 201).

The problems start once I create a new custom food. Note: At this point I can choose every serving unit I like - this becomes important later 🙂 I chosse 'gramms' as serving unit. When I hit save/submit, the backend returns the status code 400, which means 'Bad request'. This normally indicates that the client put his request against the correct endpoint, but the content of the request is not correct. And indeed, the response message is a follows:

{"errors":[{"errorType":"validation","fieldName":"defaultServingUnit","message":"Default serving unit is required."}]}

Interesting, let's take a look at the request body sent by the app:

name=Myfood&defaultServingUnit=&defaultServingSize=1.0&calories=999&brand=mybrand&saturatedFat=0&sodium=0&totalFat=0&caloriesFromFat=0&potassium=0&sugars=0&dietaryFiber=0&protein=0&transFat=0&cholesterol=0&totalCarbohydrate=0

And indeed, there's no value for 'defaultServingUnit' given, which leads to the error message.

From this point on, every food logging leads to a strange behaviour of the app: Instead of logging the food (regardless of the food being from the database or quick calories) the app tries to send the request for creating the custom food again and - such surprise! - fails every time. Also when trying to create new custom food, there is no way to select a serving unit any longer.

Now the food logging of the app has become unusable 🙂

Hope this helps when trying to fix the app @LizzyJ 

[TripleDeuce222]

Nice... that would concur with my findings as well. Although, I never took it down to the level of the network traffic. My guess is there is some kind of request queue that needs to happen in order (custom foods before food logs, which would make sense). The custom food keeps failing and retrying, thus preventing any future foods from being logged. So now we all (including Fitbit) know in detail what the problem is. Fitbit just needs to fix it. Nothing like doing their work for them while we wait. LOL.

[Nat30]

They really should be paying you for this level of investigation and information!

[MichaelBoehnke]

Haha, that's very nice of you 😊

But what they really should do is

• have automated tests, so an app, which doesn't work with the backend, does not get rolled out via PlayStore
• be able and willing to investigate such a problem themselves

[MizCat]

I have been following this conv for a while. Although I am having some issues with logging food they are not as bad as others have reported. I have not lost any entries, recent or frequent foods, custom foods or daily food logs. I have not been able to create new custom food in the app and from time to time numbers don't add up. But the following has helped. Create new custom food in the fitbit.com dashboard. Add to yout database and log the default of one serving. Log out. Go back to app and entry should be there. Edit entry to change 1 serving if required to grams, cups etc. Those options are now available. And save. If still an issue with numbers or nothing showing on tile etc. Log out of app and then log in. All should be okay. You may, however, lose an entry or two from that day or the day previous. When this happens i just re-enter. Hope this makes sense and helps someone, even the "team" working on the problem. Seems like a lost link between app and the website. The only other thing I have noticed is that you cannot edit a food item on the website. The item gets hung up and just keeps "loading'.

[W_D_S]

Hi! Question: is this error also relevant in the IPad version of the app? I have a Droid & an IPad so if the food log works correctly for Apple then I'll just log my food there until a resolution is found for the buggy Android app. Thx a bunch!!!