06-23-2022
02:35
- last edited on
07-08-2022
14:15
by
RodrigoMFitbit
06-23-2022
02:35
- last edited on
07-08-2022
14:15
by
RodrigoMFitbit
I love logging food on the Fitbit app, and enter quantities primarily by weight. When it comes to foods I can't find in the database, I create them with a serving size of 100g, and enter the nutritional info accordingly, and then when I eat that food, I just put in how many grams of it I ate.
This has always worked well for me, and I've not had any issues in the past.
However, since yesterday (22/06/22)'s update, any custom foods I create are then only available in "servings" and I cannot change the units to grams (or anything else).
This means that I can only enter my portions in multiples of 100g! What if I eat 125g of my favourite yoghurt?
Please fix this bug?!
*edit- I have gone back into the app and checked that I can enter decimals, so I can eat 1.25 servings of my favourite yoghurt. It's not ideal though, and I'm sure even more fruatrating for people who use the Imperial measurement system. A fix would be highly appreciated!
Moderator edit: Subject for clarity.
Answered! Go to the Best Answer.
07-08-2022
14:16
- last edited on
06-07-2024
11:12
by
MarreFitbit
07-08-2022
14:16
- last edited on
06-07-2024
11:12
by
MarreFitbit
@CaityA Welcome to the forums. Thanks for reaching out regarding the food log on the Fitbit app and the detailed explanation.
Please note that there is currently an ongoing issue with this tool overall. I imagine that is the reason your logs are also affected. This has been reported already and Fitbit is working on a solution. We very much appreciate your patience. Keep your Fitbit app updated to get the latest releases.
07-08-2022
14:16
- last edited on
06-07-2024
11:12
by
MarreFitbit
07-08-2022
14:16
- last edited on
06-07-2024
11:12
by
MarreFitbit
@CaityA Welcome to the forums. Thanks for reaching out regarding the food log on the Fitbit app and the detailed explanation.
Please note that there is currently an ongoing issue with this tool overall. I imagine that is the reason your logs are also affected. This has been reported already and Fitbit is working on a solution. We very much appreciate your patience. Keep your Fitbit app updated to get the latest releases.