08-18-2025 19:03
08-18-2025 19:03
A search did reveal this Topic from 2022 which has potential fixes:
https://community.fitbit.com/t5/Healthy-Eating/Log-Food-Bugs/m-p/5259674#M18378
Those fixes are basically Clear Cache, Clear User Data, and/or uninstall/reinstall the Fitbit app.
Does anyone know if clearing the User Data or uninstalling/reinstalling deletes the CUSTOM foods one may have added?
I am thinking not, but I can make it a few more days just working around the issue and waiting to see if anyone has experience with this. It also would not be a show stopper if it does delete as the default database is now inclusive of most foods I eat and my eating habits have shifted enough there are less than a handful of foods I would need to add back.
I'm using Android:
Fitbit app:
Charge 6 System/firmware:
Answered! Go to the Best Answer.
08-21-2025 09:38
08-21-2025 09:38
For my Fitbit App, I just finished clearing the Cache and clearing Storage.
I had to go through the initial setup to re-pair my Charge 6 with my Fitbit App, however this appears to have resolved my RECENT Foods issue. Also my CUSTOM Foods were all retained.
08-21-2025 09:38
08-21-2025 09:38
For my Fitbit App, I just finished clearing the Cache and clearing Storage.
I had to go through the initial setup to re-pair my Charge 6 with my Fitbit App, however this appears to have resolved my RECENT Foods issue. Also my CUSTOM Foods were all retained.