07-11-2018 11:19 - edited 08-14-2018 15:02
07-11-2018 11:19 - edited 08-14-2018 15:02
Update 7/19/2018: This issue is now resolved, please ensure your app is updated if you still experiencing this issue. We appreciate everyone's patience and cooperation as we worked on a fix. I'll be closing this for further reports. If you are experiencing any new issues with food logging, please start a new thread.
Update 7/18/2018: Thanks again everyone for your reports. Glad to hear the update has corrected food logging issues for many.
If you are still experiencing this issue, we would love to investigate further. The following would help our team review:
We appreciate the additional details.
Fitbit Update 07/16/2018: Hey everyone -- We have just released an update to the Fitbit app for iOS, version 2.53.1 which we believe resolves the issues with food logging that have been reported in this thread. Please update to 2.53.1 and let me know of the results so I can quickly communicate that to our iOS team.
Again, thank you for your continued patience as we worked to get this resolved ASAP.
Update 7/15/2018:
Thanks everyone for your patience on this. We sincerely apologize to anyone who has been affected by this issue and have been working hard to find a fix. We are preparing to roll out an update tomorrow, July 16th to solve the problem. In the meantime, customers can use the food logging feature in the web dashboard: https://www.fitbit.com/foods/log.
Update 7/14/2018: We do realize this is a critical issue and our team continues to work on the cause and a fix. We don't provide timelines, in case something occurs and it can't be met, but we hope to have a resolution soon. Thank you again for your patience, reports, and cooperation.
Update 7/13/2018: Hi Everyone - we definitely do hear your reports and frustration on missing and strange food logs. Our engineers are still investigating and I hope to have a resolution shortly.
While not ideal, you can log on Fitbit.com food log and it will populate on iOS correctly once you sync. You can log it here. We appreciate your cooperation. I'll continue to update this thread as I hear more.
Update 7/12/2018: Hi Everyone - thanks again for your reports. We are actively reviewing this issue and I'll continue to update the thread as I hear further. As a workaround you may want to log your food through https://www.fitbit.com/foods/log. As mentioned in @sreid64's post, it will populate the iOS app correctly. Thanks again for your patience and reports.
Update 7/11/2018: Hi Everyone - I've merged a few posts together. We are currently investigating issues with food logging on iOS version 2.53. Please continue to monitor this thread for updates. If this is severely affecting your food logging, you may want to log through Fitbit.com. Thank you very much for your reports and patience as we review.
Actively managing your weight? Find accountability buddies on the Manage Weight board
Answered! Go to the Best Answer.
07-15-2018 22:40
07-15-2018 22:40
When I enter food it appears for a split second then it goes but the calories have knocked off still. When I shut down the app and re open it, the calories are back on.
I’m getting fed up with doing it on the main site as I think it’s much more complicated and time consuming. I hope they hurry up and fix it. I wish I never updated it!!
07-15-2018 22:43
07-15-2018 22:43
07-15-2018 23:16
07-15-2018 23:16
For those posting here recently and who may not have read the earlier posts, the main thread for this problem is at: https://community.fitbit.com/t5/iOS-App/Issues-with-food-input-on-iOS-2-53/td-p/2825777
Fitbit will be updating that with any news and are unlikely to update this thread.
07-15-2018 23:21
07-15-2018 23:21
Keep an eye on the main thread - it looks like they are close to a fix
07-15-2018 23:22
07-15-2018 23:22
Fingers crossed!! 🙂
07-15-2018 23:23
07-15-2018 23:23
07-15-2018 23:34 - edited 07-16-2018 00:05
07-15-2018 23:34 - edited 07-16-2018 00:05
Couples things. One, I pointed out this wasn't customer service because some of comments that were posting were that people aren't getting responses from customer service to their posts in the forum. I read at least 25-30 posts where people thought this was a direct link to customer service. So I was correcting that information. Though you must know, this chat is a group of users in community discussions, a lot of people thought this was a direct way to talk to customer and were confused by lack of reply. Also, for general information if you ask them wrong person, you won't get the right answer... this is community chat and not customer service so they really can't help you.
Also, the reason a lot of comments were deleted were they violated policy. I don't mean to insult some of you, but if I offered a community discussion of my products I would have a policy where I could delete ones that I didn't like. I wouldn't word the policy like that, but if you think a company designed a community discussion without some kind of safety net, you're not that bright. So if something was deleted if went against the rules which users agreed to use the chat. Read the rules and follow them. If you broke the rules, that you agreed too and they held you accountable then your complaint should not be, "they deleted my comment because they didn't like it", but "Wow, they caught me breaking rules that I agreed too and held me accountable. I should be a better person in future and keep my word because I wouldn't teach my kids to break their word for selfish purposes."
Also, the fact that a problem with an update wasn't fixed within 4 days is not outrageous. The lack of patience of grown adults over an inability to log food for 4 days is outrageous. This is what the rest of the world makes fun of us for, calling it "first world problems". Not a single one of you would tell your kids that an inability to use an app that is for convenience not life ending for 4 days deserves this kind of outrage. This is not a life saving app, this is a convenience app. The fact that so many adults are throwing tantrums over this, is depressing and pathetic.
Grow up and calm down. Their workers are not slaves and fixing problems are not instant. This is an overreaction to what really is nothing.
07-15-2018 23:36
07-15-2018 23:36
@Rosey55 the problem that I think this thread refers to only affects food logging - all other functions are fine and fitbit are aiming to release a fix to food logging today (16 July). See: https://community.fitbit.com/t5/iOS-App/Issues-with-food-input-on-iOS-2-53/td-p/2825777
07-15-2018 23:37
07-15-2018 23:37
Keep an eye on the thread that banner links to:
https://community.fitbit.com/t5/iOS-App/Issues-with-food-input-on-iOS-2-53/td-p/2825777
Fitbit have recently updated it with the date the fix is expected to be rolled out
07-15-2018 23:43
07-15-2018 23:43
Keep an eye on the main thread for this issue as that's where fitbit will be posting news:
https://community.fitbit.com/t5/iOS-App/Issues-with-food-input-on-iOS-2-53/td-p/2825777
Seems like a fix is coming today (16 July)
07-15-2018 23:46
07-15-2018 23:46
Thank you for the update. Can’t wait to be back to ‘normal’ again! Didn’t realise how much a part of my daily routine logging food had become. Sadly lost without it!
07-16-2018 00:10
07-16-2018 00:10
I think they’ve suffered a data breach. They wouldn’t be the first fitness app to have something like that happen. Fitness apps have a LOT of personal data; it’s a potential goldmine. I think the reason for the inconsistency is that they’re covering it up. The reason they won’t roll back is that they’re uncertain about the security of that version, too.
I suggest everyone check their email address and look out for suspicious activit, and change their password.
07-16-2018 00:14
07-16-2018 00:14
07-16-2018 00:17
07-16-2018 00:17
I have the same problem, no mater what food I enter it changes to chicken in red wine
07-16-2018 00:18
07-16-2018 00:18
07-16-2018 01:17
07-16-2018 01:17
I hope this gets fixed soon! I am also having the issue of logs having the disappearing act as well as my logs showing up as something completely opposite when they are enetered. Like my bacon is turning into cheesecake. Lol
07-16-2018 01:52
07-16-2018 01:52
This problem isn't only on the app - when logging a glass of wine on my computer cos the app doesn't work it logged as several thousand calories. I know drinking isn't great for me but really....!
07-16-2018 02:17
07-16-2018 02:17
It has now more than 4 days... when will the issue be solved?
07-16-2018 02:20
07-16-2018 02:20
Good day
Good that you are looking into the iOS issue.
Maybe you can use the experience to also look at the Andoid portion/measurement-reset bug? https://community.fitbit.com/t5/Android-App/Logging-food-resets-portion/td-p/1158663
This thread has been started in 2016 and it is still an issue...
With every update I hope for it to be fixed
07-16-2018 02:22
07-16-2018 02:22
Same issue here! Awaitibg bug fix!