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 14:32
07-15-2018 14:32
07-15-2018 14:34
07-15-2018 14:34
07-15-2018 14:37
07-15-2018 14:37
07-15-2018 14:40
07-15-2018 14:40
07-15-2018 14:44
07-15-2018 14:44
07-15-2018 14:45
07-15-2018 14:45
07-15-2018 14:49
07-15-2018 14:49
Thankyou. I’ll keep an eye on it.
07-15-2018 14:51
07-15-2018 14:51
We really apologize for any inconvenience this has caused. It's still an ongoing issue that our team is prioritizing a fix for.
We will continue updating this thread to provide any new information. For the time being, we would just like to reassure you this is being worked on as quickly as possible. Thanks for your patience and cooperation!
Thank you @AlessFitbit for giving us an update - unfortunately, it doesn't really give us any new information over and above what we had last Wed/Thurs.
Perhaps you could provide us with some answers to some of the questions that keep coming up here time and time again?
Firstly, we know that Fitbit made a choice not to rollback to the previous version. (that was stated several hundred posts back by a member of the team). To many of us that appears to be a very strange decision. I am sure they have a good reason for it. If you can tell us why that decision was made it would go a long way toward reassuring your users.
Secondly, please can you give us some indications as to what went wrong to cause this. You don't have to tell us in detail, but please tell us something. This forum is rife with conspiracy theories that Apple have caused it get everyone to buy Apple Watches (which I don't believe for one moment BTW) or that Fitbit was hacked and all our data was taken (I know this was denied but with without any other explanation I can see why some are still suspicious)
Thirdly, can you tell us how you intend to inform us of when the fix is released? Visiting this discussion thread is becoming a very inefficient way to get information. There are literally hundreds of post to each day (mostly by justifiably angry users) that it is very difficult to find the occasional post from Fitbit in the middle of 40+ pages. Subscribing to the thread is just flooding my inbox with email notifications. Will Fitbit commit to emailing us? (you have our email address when we signed up to your service).
It doesn't matter what size the organisation is from the smallest one-man-band to the biggest multinational things WILL go wrong at some point. The reality is that users don't judge an organisation on what went wrong they judge it on how they respond to it. It is very, very hard for any organisation to admit they got it wrong - but if history tells us anything companies that get the most respect from their users are the ones who 'fess up, say "sorry", and keep their users informed about what is happening every step of the way. At the moment Fitbit isn't doing this and you only need to read this thread to see that people are leaving in droves.
Let me be honest, I am a new user - had this happened two weeks ago ie before I had purchased, I wouldn't have bought a Fitbit - not because of the problem but because of how Fitbit has handled it.
Signed,
A worried new user
07-15-2018 14:52
07-15-2018 14:52
07-15-2018 15:16
07-15-2018 15:16
I posted to the CEO on twitter asking that he or some executive become involved with communicating.
07-15-2018 15:24
07-15-2018 15:24
I have no idea what you regard as an update but continually telling us the issue is being worked on isn’t really an update. It’s unbelievable that this has not yet been resolved.
07-15-2018 15:25
07-15-2018 15:25
07-15-2018 15:34
07-15-2018 15:34
07-15-2018 15:47
07-15-2018 15:47
I also cannot log my food. This is very frustrating. Just found out this is an issue from a live chat person who was no help. She said this could take days yet and they won't email me when it's fixed. So I have to keep trying to log food or go online to log food (I tried this and it didn't work). Waste of time. Very disappointed in FitBit. My husband wanted one for when school starts again but I'm not getting it from FitBit . I"m going to look into other products. Seems like this shouldn't take so long to fix.
07-15-2018 15:49
07-15-2018 15:49
My has been doing this for 3 days I put in cerise it logs cranberry and banana or Tako please fix now
07-15-2018 16:03
07-15-2018 16:03
It's not a hack. On Wednesday morning (07/11), food logging was working. After upgrading the Fitbit version to 2.53 on Wednesday, it no longer worked. That's an app development issue. The fact that five days have passed without resolution is a problem. Yesterday, it seemed liked they knew the cause but didn't have a fix. Today's update made it sound like they don't know a cause and don't have a fix.
Also, the process that Apple follows to review apps for the App Store can take several days. It would not surprise me if there wasn't a new version out there until Wednesday. They should have reverted back to 2.52 if possible.
07-15-2018 16:05
07-15-2018 16:05
Thank U guys for sharing , if this problem isn’t fixed soon we need to look for a new product. Also, I have a problem with notifications & messages. I haven’t received any notification messages since 6/14/18
07-15-2018 16:06
07-15-2018 16:06
07-15-2018 16:09
07-15-2018 16:09
I'm having the same issue
07-15-2018 16:19
07-15-2018 16:19
I really have to question if Fitbit has a real IT department that knows what they are doing! 4 days without the Food Log not working is totally Unacceptable! If this is suppose to be a quality product on the front end the back end ( IT ) needs some major investment! The PR this is causing and the lack of communication coming out is not that great either! I am really disappointed that a company like this can't fix their own created error.......Send this IT problem over to Apple and have them fix it now!