Issues with food input on iOS 2.53

[KateFitbit]

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:  

• • Are you already updated to 2.53.1? 
  • What is the OS version that you are running on your iPhone?  
  • What food database are you using?(See Account>Advanced Settings>Food Database).
  • What language are you using the app in? 
  • What foods are you trying to log? 
  • What specific interaction are you doing that is not working? (Adding, editing, deleting, scanning).
  • What time/date did you see the issue? 

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. 

[DaveMo]

I'm about to be reimbursed for the (unopened) Fitbit Ionic my wife just bought me for my birthday.

[Bokat76]

Exactly, probably not a "hack". Anyone thinking, hmm, Apple sells a
competing product and Apple's operating system is the only one experiencing
compatibility problems with Fitbit. Coincidence?

[Nk94555]

Does Apple Watch tracks burned calories and hearbeats? If it does or any
other device, I am going to buy right now. Fitbit is a joke.

[Vette4ever]

Your message says to log food via dashboard, that’s the only way I’ve ever logged food. Is there another way ? 

[AlessFitbit]

Hi, everyone!

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! 

[DaveMo]

No, I haven't thought that even once.

Fitbit IT has a major screw-up here. Even if the Apple conspiracy theory is true, Fitbit still did not test it before it was foisted on us. Fitbit screwed up. No one else. And they're silent about it, which is the real insult to those of us who bought a product that we're not getting at this point.

[ChrisB_UK]

Have to use website rather than IOS app. The latter is much easier.

Moderator edit: personal info removed

[VercE]

I also work in it. I can not believe that fitbit personel don’t care about what happend. 

Yes it is not greatbto have this problem but I believe that they would have already solved it when they found to problem. No?

only question I have if going back to previous version is possible but even that is not always possible in it. 

Let us put Some trust in the people. How would you react when ecerybody kept complaining when you are trying to solve a huge problem?

[SunsetRunner]

Hardly. Previous version of app worked fine on latest version of iOS. Fitbit’s broken update was the problem. Problem showed immediately meaning their testing was inadequate before they released it, and they didn’t provide an immediate rollback. Bad development process.

[Richned11]

This really is unacceptable. It's just not practical to have to use a laptop when food entry is a feature you regularly use. This will affect my decision to upgrade to a newer fitbit. I may try something else unfortunately after having had one for more than 2 years. Inconceivable that a fix can't be quickly found after what was a pretty dreadful release of an update with such a serious bug. Sorry.... a bit frustrated.

[Bsquirrel]

Besides not log food properly, I stop getting update notifications on 6/24/18

[Vette4ever]

Your message says to log food via dashboard, that’s the only way I’ve ever logged food. Is there another way ? 

[SunsetRunner]

Because Fitbit didn’t broadcast a notice to all iOS users that the latest update was defective, nor did they take down the bad update, nor did they roll back to previous version in App Store, we have all wasted our time discovering this bug and trying to fix it on our own, then discovering finally this as the only source of information.

Really bad sloppy shoddy treatment of customers.

[SunsetRunner]

@Nk94555

It does track workouts, calories & heart rate. The reason I stuck with Fitbit so long was because you could track food in the same place. The apple watch food tracker app is my fitness pal. Now we have Fitbit recommending MFP as an alternative to their non functioning app so we might as well make the switch. My mom, cousin & best friend have been harping on me to make the change & this just sealed the deal.

[richlippert]

Hello, I am also having the same issues on my iPhone iOS 11.4.1

It started on Wednesday or Thursday last week that I noticed.

Rich

[Nk94555]

@SunsetRunner Nice I think if it doesn't get fixed by tomorrow then I am going but apple watch tomorrow. But is apple watch accurate for tracking heartbeats and burned calories? https://www.kirkville.com/how-accurate-is-the-apple-watch-as-a-fitness-tracker/ - It's not very promising review.

[ShelbyBu]

Unfortunately I also continue to have difficulty inputting food on Fitbit App- hopefully you will fix it ASAP. Finding it quite frustrating. 

[SunsetRunner]

@Nk94555 

No, it’s definitely not ideal. The heart rate on my versa has the same issue though. 

[Bsquirrel]

Beside food register issue, issue with notifications on update with steps & excercise. Has not registered since 6/14/18

[Michelle107]

Yes, same issue with food tracking.  In spite of the appreciated updates from FitBit on this issue, the time it's taking to fix is frustrating.