Bug: Nutrition Facts page does not calculate macros based on serving size

[callousparade]

The Nutrition Facts page incorrectly calculates macros. I can create and resolve the bug on demand.

Problem: 

The Nutrition Facts page assumes all food is logged as a single serving, it does not perform math based on user's portion size inputs like it should. 

Evidence 1

All food in the following screenshots are logged as 1 serving. The Nutrition Facts page is correct and it agrees with the Macro information displayed on the Food Page. This is functioning properly.

 

 

Evidence 2

Now I have changed my Almonds to reflect ½ serving. The nutrition page is unchanged, it still reflects 1 serving of almonds, and everything else, which is now incorrect. However the macro info on the food page has updated properly.

Evidence 3

Now i have changed my log to reflect 10x servings of everything. Again the nutrition facts page still reflects 1x serving, which is incorrect, while the macros info on the food page is correct. 

 

 

Summary

The app is not performing the portion size calculations at all on the Nutrition Facts page. Anything logged as 1 serving is properly calculated, but anything logged as greater than or less than 1 serving does not have math performed on the nutrition facts as it should be.

more info

Verified on: pixel 3, pixel 1xl and samsung galaxy note 10. All running the most recent app version from the Google play store

I did the app uninstall and reinstall process that the support faq recommended on all three test devices. No change.

It is not a matter of the nutrition facts page needing to refresh, any new foods added to the log are immediately reflected (as one serving) on the nutrition facts page.

[callousparade]

If thread is misfiled or not allowed please let me know why this time. It's a very irritating bug for those of us tracking macros and I've spent some time figuring it out and writing this up, please don't archive it without comment.

[markusw1]

Nobody here who can tell us anything about this issue ?

[RedMom3]

Looking for a solution to this as well!

[Smiggs99]

Thanks for the post.  I wonder if it ever worked(I only just started using it) or if this is new bug.  Either way, thanks for your post.  At least now I know which page is incorrect in the meantime. Hope they fix it soon. 

[Evelinezernetzk]

This is the same issue I've had since I started using a fitbit over 5 years ago. Odd that my husband's app on his iPhone correctly adjusts the nutritional components correctly.  Need a fix for android version. 

[GalaxyOtter]

I came here to say something about this issue as well. I'm glad to see someone has already made this thread. It seems ridiculous that the app can't do simple math. It is also really irritating. I.m finding that the nutritional information is correct but the macronutrients on the main page is incorrect.You can see in the following two images that the data does not match. I did the math for the 3 things I had consumed so far when doing this and the Nutrition Facts page is mostly correct (total carbs should have read 9.8g I'm guessing there were some carbs at 2 decimal places and this has been rounded up...), but the Macronutrients page is nonsence.

 

[DocGuitar]

My wife just reported the problem on her Android.  version 3.41.2.  My Android version 3.39.2 computes correctly,

It appears that 3.41.2 takes the values in the database as nutrients per base unit of the entry then multiplies by the number of units.  My wife's count for 4 oz of Panda express white rice took the Panda values (which is for 8 oz) then multiplies that by 4 ! she was shocked at the protein and sodium in 4 oz!

Someone at FitBit needs to do a system specification of the database and make the program's arithmetic consistent.  It looks like the new version was  changed to "fix" the "multiplication" problem for nutrients by just multiplying the database value by the quantity without any thought or analysis.

[callousparade]

Yeah after like 5 years of this issue being completely consistent (has anyone mentioned how absurd that is?) something finally changed. Now it's much worse and the pattern of wrongness is now inconsistent. The macronutrients information on the food page is correct while the nutrition info page is always way way higher and incorrect.

So whatever y'all just did a month ago... You messed with the right bit of code but didn't fix the ish. go ctrlZ and try again. It's just straight up absurd that years have gone by without this silly wellness tracking app fixing a massive math problem in its food tracking.

[PauH]

Same issue here.

In addition to that, maybe I am missing something, but the % of each macro doesn't match/add-up to the total grams ?

The app currently shows 34% carbs (221g), 41% fat (111g) and 25% protein (150g) - which doesn't make sense because, for example, fat should be 22.9% of the total macros ? Am I missing something here ? 

[callousparade]

I can explain that one at least. It doesn't clarify this anywhere but the percentages are based on calories instead of grams. Fat has 9cals per gram, protein and carbs both have just over 4. So that's where the percentage math is coming from

[callousparade]

Hurrah, it appears fixed as of update 3.43! Most excellent