Frequent food added as anytime, not breakfast

[Kelly1407]

For the past week I’ve been having issues logging my usual breakfast food items. They now all need to be added individually and changed from ‘anytime’ to ‘breakfast’. It’s time consuming and frustrating. Yet all lunch, dinner and snack usual food items allow me to select what I usual eat with eat item. How can I resolve this please?

Moderator Edit: Clarified subject

[LizzyFitbit]

@Kelly1407 Welcome on board.

I'm sorry for the inconvenience you've experienced while logging your good. I understand where you're coming from as this isn't the expected behavior of the food tile. Because your post didn't mention, may I know the model of your phone? Do you recall if this started happening after updating the Fitbit app?

If you've not done so, I'd recommend the following steps:

1. Log out from the Fitbit app.
2. Force quit the Fitbit app and reboot your phone.
3. Open the Fitbit app and log into your Fitbit account.
4. Pull down on the screen to force a manual sync.
5. Try logging food one more time to see how it goes.

Hope this helps.

[Kelly1407]

Hi Lizzy,

I’ve tried your suggestion however no joy. I’m using the app on a iPhone 11 Pro Max. I’ve stopped logging food for now as I don’t have time to do this one by one. 

[rfowlie]

I’m having the exact same issue too and it’s been driving me crazy! Breakfast only and the items show anytime and won’t auto group. I eat virtually the same thing every morning and it’s so annoying to do it one by one versus how easy it used to be. I’ve tried all the above-noted suggestions and it hasn’t resolved it. This did start to happen after the app recently updated. I’m using an Apple 11 phone. 

[Kelly1407]

I thought it was just me! There must be others having issues too. We seem to be using the same phone too. I’ve stopped logging my food until this issue is resolved. I hope it gets sorted soon 🤞

[LizzyFitbit]

Hi @Kelly1407 and @rfowlie. It's good to see you here in the forums.

Thanks for getting back with the requested information, as well as trying the suggestions posted above. I'm sorry for the inconvenience you've experienced and I've forwarded your posts to our team so they can investigate what may be occurring. I'll update this thread as soon as I have more details from them. Make sure to keep the Fitbit app up-to-date to ensure your data is logged correctly.

See you around.

[Spazz_Dad]

Any updates from your team on this issue?

[Kelly1407]

No updates as yet 🤷🏻‍:female_sign:

[LizzyFitbit]

Hi @Spazz_Dad. Welcome on board. @Kelly1407 It's good to see you again.

Thanks for your continued feedback about this situation. This issue with the food log has been reported to our team so they can work on it and improve the features on the Fitbit app. I understand how this may be affecting you and while I don't have further details from them, I'll keep the informed of the impact to you and other members. Your patience is truly appreciated and rest assured your feedback hasn't gone unnoticed.

See you around.

[Kelly1407]

Thank you 🙏🏻 😊

Sent from my iPhone

[rfowlie]

I’ve also noticed issues with my alarm clock not working since this started too. A couple days it didn’t go off and auto-snoozed for hours without vibrating. Have you experienced that in connection with these breakfast logging issues too? It’s like all of a sudden my FitBit isn’t a morning person anymore. 🤣

[Kelly1407]

😂 No I haven’t experienced this

Sent from my iPhone

[rfowlie]

Any updates on this?  Logging breakfast is such a pain, particularly considering I have almost the same thing daily and have to input each item individually now. 

[BridgetKlish]

Hi all,

Here’s my issue. I eat a bagel with butter for breakfast most mornings. Usually what should happen is I select the bagel from my recently used items, and on the screen where I select the meal and quantity, it should auto-select breakfast (since that’s the meal I most recently ate it for) and underneath it’ll have butter as “recently eaten with.”

But what’s happening instead is it comes up as “Anytime” and doesn’t have the butter saved as a paired item. 

This ONLY happens when I input items as breakfast. I tried inputting them as “morning snack” yesterday and it came up under that today, with the butter paired like normal. It worked when I did it under dinner, too, so it seems like something is messed up with the Breakfast coding.

@Fitbit, can someone please fix this bug? Quitting the app/restarting my phone doesn’t fix it and it’s been happening for weeks. 

[LVinLA]

@Kelly1407  @rfowlie  @Spazz_Dad @BridgetKlish 

I'm having the same problem on my iPhoneX, iOS 14.7.1.

One workaround I've found is that if there is one item in your breakfast menu that you can scan a UPC code (rather than selecting from the "Frequent" or "Recent" lists), it will properly show up as "Breakfast" with the "Previously Eaten With" list. Still kind of a pain, but MUCH more convenient than entering each item one by one.

[rfowlie]

Thanks for the work around suggestion!

[Sengsb]

Is anyone finding when logging food, breakfast regularly logged foods are not being grouped as previously logged, so every item comes up as anytime and you can’t do a meal in one submission? Lunch and dinner don’t seem to be affected, just breakfast. Any suggestions to fix it?

Moderator edit: label

[LiliyaFitbit]

Welcome to the Fitbit Community, @Sengsb.

Thanks for the details shared in your post. I understand your concern and would like to confirm that this issue has been reported to our team and they are currently investigating it. I've merged your post to this thread for more information. I am sorry for any trouble, thank you for your patience and understanding. 

See you around.

[mstonge70]

I want to keep this thread active. I am having the exact same issue with breakfast food. No memory what so ever of what I have eaten before. I must add them one by one because the default is Anytime and it doesn’t remember groups previously eaten together 

[Spazz_Dad]

I’ve received multiple app updates over the past several weeks, but none of them have corrected this issue.  I’m beginning to think the developers have no intention of fixing this problem.  

Have they abandoned development of the food tracking in the current app and working on a replacement instead?