Decimals disappear from Custom Food entries

[Aailski]

I seem to have a problem that whenever I add custom foods with decimals, within a day or two, all the decimals disappear and the log shows a number of "Uncategorised Cals" instead. What is the problem here? Generally if I go in and re-add the decimals (not always easy if I no longer have the label!), they tend to stay in.

[AlvaroFitbit]

@Aailski It's great to see that you've visited the Fitbit Community!

Let me help you with your food logs. Try logging out from the app, resart your phone and log back in. After this please retry logging your food.

Let me know how it goes.

[Aailski]

Hi, no, it's still doing it, whether I log on the app or desktop.

Get Outlook for Android

[Cut]

I have also noticed this bug (in the Android app). It is intensely annoying.

Related (and why being able to create accurate custom foods is so important...): most of the non-custom food entries (at least in the Spanish database) are incorrect because of the strange decision by Fitbit to measure sodium in milligrams but potassium in grams.

Are these known bugs?

And what is the timeline for a fix?

Cheers

[Aailski]

I have noticed the sodium is in mg here, but we measure salt content on labels in g, which makes me wonder if the database is still geared toward US counterparts.

Also, the "uncategorised" Cal's is unhelpful when it doesn't tell me which food it is - and I don't know what's uncategorised!

It certainly needs a fix.

Get Outlook for Android