I am reupping per @NYL and the many others who've posted here; this is is not resolved and shouldn't be marked as such, as the "Best Answer" is no answer at all -- it takes 4x the actions and more than that in a time to increase time to navigate to custom foods, click the custom food, and click to log it, and then quantify it, which is what happens when you go to Custom food as the "Best Answer" suggests. And this issue is persistent, for me as well, across web, iOS, and Android platforms. And yes I have tried all the fixes suggested with the apps, logging out, reupping page caches, etc.
In terms of ease of use, it's a significant hindrance for anyone tracking and customizing food; it's central enough to this part of the user-experience that I will consider changing services when the time comes for a new device if Fitbit is unable to solve it, since "logging food" is obviously one of the most persistent activities if you're doing it, and if you're doing it then adding Custom Foods is probably a big part of your usage. Please advise us on the status of making sure all logged Custom Foods show up in food searches from the main add page of the Food Log.
