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 06:37
07-15-2018 06:37
This is just a disapointment, now its roughly 10 days ago I bought a Ionic for me and a Versa for my wife.
Today we went for a walk using GPS traking. Me with the built in GPS, she was using the phone GPS linked to the Versa.
It was a one our walk, mine was logged with a length of 7.25 KM and her's was logged with 6.4KM.
When comparing the maps both maps match perfectly, so we can exclude that one of the GPS signals got lost.
What's the problem? Why that huge discrepancy?
Really, I'm so disapointed by the quality of these products.
07-15-2018 06:42
07-15-2018 06:42
New food not saved for at least 3 months, and since yesterday not saving any food, I have entered breakfast and lunch 5 times today and nothing saved, and now at syncing the 250 steps an hour correctly, my ionic at this minute says 8 from 12 which is correct, but on my iPhone 7 Plus says 7 from 12, same happened yesterday and the time it says was at 11 am and I was on a 6 mile walk at this time ??? It is also saying 66 minutes walk, even ionic says this yet the dashboard shows I walked 1 hour, 36 mins and 37 second this morning, yesterday it states I walked 62 minutes, yet dashboard map shows I walked for 1 hour 15 mins and 45 seconds, so fed up of this have had issues in past and now seriously thinking of changing to a watch that counts correctly
07-15-2018 06:53
07-15-2018 06:53
Fitbit, it’s now been 4 days since the app update that caused the food logging issue. Your workaround using the dashboard is not viable as it’s a terrible interface. I don’t want to download another app just to feed data into yours.
please can you just accept this latest update hasn’t worked, roll back the change to the last working version, and properly test future app releases? Surely food logging isn’t a pretty fundamental part of your app, and you have a pretty big issue in your testing process if these problems weren’t noticed.
07-15-2018 07:10
07-15-2018 07:10
It has been since13/07 that even synchronization of steps and sleep has gone kaput!! It always say looking for alta hr but it cannot find and synchronise.
The alta hr is just beside the iPhone and it cannot find the tracker.
How do you expect me to log the sleep on fitbit website?
07-15-2018 07:32
07-15-2018 07:32
Can’t you put us back to the last update until you fix this issue???
07-15-2018 07:48
07-15-2018 07:48
Any idea on how long this fix is going to take?? It’s really quite annoying.
07-15-2018 07:49
07-15-2018 07:49
Please fix this. I put in Cheerios and get Dried Cherries.
07-15-2018 07:52
07-15-2018 07:52
07-15-2018 08:01
07-15-2018 08:01
07-15-2018 08:07
07-15-2018 08:07
I agree, we are waiting to long now, put the right people in the right place so this will be fixed now or give us back the version that worked.
This is really disturbing!!
07-15-2018 08:13
07-15-2018 08:13
iOS 22.55.2 problem. when scanning bar code, data is displayed correctly then it appears under time of day (lunch, dinner, etc.) very briefly. at this point it disappears. tried on iPad, iPhone same problem. had to search web for nutrition data, and enter it manually.IOS 22.55.2 on iPad and iPhone.
07-15-2018 08:23
07-15-2018 08:23
I was able to log most of my food yesterday on my iOs App. A few foods dropped off, but most were able to be logged.
I appreciate what everyone is going through, but I also understand that there can be issues with any tech. This is a pain, but I believe it will get fixed sooner rather than later and in the meantime I will continue to try to keep my entries on the phone app.
07-15-2018 08:27
07-15-2018 08:27
For anyone else who may be following: only the premium (paid) version of the Lose It! app will connect to FitBit. The free version of My Fitness Pal syncs to FitBit, but is a bit crappy and ad-filled.
07-15-2018 08:29
07-15-2018 08:29
And you know we aren’t getting reimbursed by Fitbit lol
07-15-2018 08:32
07-15-2018 08:32
07-15-2018 08:35
07-15-2018 08:35
07-15-2018 08:36
07-15-2018 08:36
07-15-2018 08:39
07-15-2018 08:39
I continue to have problems logging my food. It's been going on since Friday, 7/13/18. When I enter a food something completely different shows up in my log, so then I have to manually enter it through Fitbit.com, which is a little frustrating and inconvenient. Is this issue still being worked on?
07-15-2018 08:41
07-15-2018 08:41
07-15-2018 08:52
07-15-2018 08:52
This is probably related to ongoing bug with food logging. Keep an eye on the following thread which has the latest updates from fitbit:
https://community.fitbit.com/t5/iOS-App/Issues-with-food-input-on-iOS-2-53/td-p/2825777