Nutrition data incorrect

[pointlessuserna]

Nutrition values are still wildly broken on the latest version, and a moderator just had the audacity to close all the topics claiming it's fixed. It's been broken for months, if not years, and you can't gaslight us into believing otherwise. But you can destroy your own brand.

Moderator edit: Subject for clarity.

[Lucybrown]

as has been notes in forum with posts as old as a year 

the nutritional information for percentage RDA of example iron vitamin  vitamin c. is way off.  overly exaggerated 

example 1/2 banana listed as having 2880 % of vitamin a. 392-% vitamin c and 12 -% iron 

cauliflower 1 cup listed as 41% of iron 

5400

vitamin c

and rhese can not be fixed by adding custom food as there is no option to enter RDA

these exaggerations are across the board 

most every day shows percentages in these categories ranges 1000-% to 40000 %%.  which is way way exaggerated and completely inaccurate 

[Lucybrown]

When will fitbit correct this 

[netwolf7]

This issue was fixed with this new release today, but now the app crashes when selecting a food item stating it has a bug. I posted a new thread for this.

[LizzyFitbit · Accepted solution]

Hi everyone, and welcome to our new members.

Thanks for keeping us posted and for every step tried on your own. I'm happy to share with you that the Fitbit Android App 3.66 is now slowly rolling out to all our members and will include a fix to receive accurate reporting of Nutrients for food logging. Because this is a progressive roll out, if you don't see this update available yet, check later and install it once you do.

If by any chance the issue persists, please don't hesitate to let me know so I can keep our team informed.

[hollytolo]

Please do not close this post until we can test as users.

[LiamMac]

I got 3.66 yesterday..... the core of the macronutrient miscalculations does, indeed, appear to be fixed. 

B U T

Another user yesterday quickly established that 3.66 crashes if one wishes to scroll through one's custom foods list. Following on from that, I noted that the macronutrients chart is still reporting the wildly excessive values.....

https://community.fitbit.com/t5/Android-App/Fitbit-App-crashes-on-Android/m-p/5225230#M161407

Custom foods was heavily impacted when this whole thing kicked off in the 3.59 release in May 😞

[ChickNorris]

Hi. So the issue I'm seeing is when you look at the total nutrients you've accumulated for the day, the totals are highly elevated. Apparently, Fitbit won't let me upload pictures to show you what I mean, so I'll have to just do my best 

For this example, I'll be using a Fairlife Protein Shake. It should be 30 grams of protein and 239 mg of sodium. However, it shows under the "grand total tab" of 345 grams of protein and 2645 mg of sodium.

I hope this helps you understand the issue going on. Yes, even after the latest update, uninstalling and reinstalling several times, restarting my phone, and everything you have suggested in past threads. 

 

 

[Cshu]

Oh I know nutrients have been wildly incorrect for months but it seems the
recent update 3.66 finally seems to fix that. However with that, you can't
add custom food. There's a bug that needs fixed.

[ThatDii]

@Cshu still waiting on 3.66. 

Is the custom food tab just gone?

[Cshu]

No it's not gone but when you hit+ it self closes and says it has a bug
developers need to fix. The nutrient count seems to be fixed though.

[ThatDii]

Just got 3.66 and hot d*mn things look fixed. Keeping my fingers crossed.

@Cshu Custom food appears to be working on my end. 😞

[Ftumch]

@pointlessuserna I love the irony of them marking their answer as the best and as answered in reply to your post criticising them for doing exactly that previously

[LizzyFitbit]

Hi everyone.

Thanks for sharing your experience after updating the Fitbit app. Since most of you confirmed to have received the fix for this issue, I'm going to close this thread.

In regards to the Fitbit app crashing while attempting to log a custom food, we recommend sharing your feedback in this thread which is actively monitored by our team.

Your feedback and patience are truly appreciated, and we'll keep working to keep improving our devices, as well as our services.