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. 

[Rockinrobi9]

I’m having this issue as well. Inputting custom foods and as soon as it saves it changes to something not even remotely close in what it is or calorie content (example: changes a chicken sandwich to broiled fish). Resetting the app or phone does nothing. Is there any fix to this?

[Kallioppe]

Having the same issue.... seems to be working on the website, but the app is much easier to use. 

[HisBunny]

It would be nice to receive email reports of malfunctions when the app is not working as intended. But hopefully it is resolved soon.

[JCSask]

Thanks for answering. Yes I use an iPhone and mini.

Sent from my iPhone

[JCSask]

Thanks for getting back to me. Yes I use an iPhone and mini. 

[Karita1973]

I have the same issue.  I’m on with Fit bit chat telling them about it hoping they can fix.

[LadyDi13]

Having a hard time adding food to daily log. Not accepting old & new foods.  Tried doing a custom for the log and it changes the name and input. Also, frequent or recent foods are being changed when added. What’s gobig on?

[Karita1973]

I am havibg the same issue.  I hve a case open with fitbit chat

[ElizabethB81]

Mine too! And if I try chicken cutlet its a meatball sub. 

[jhwig2016]

I agree.  This is incredibly frustrating.  After spending $330 on this device, I hope that it gets fixed as well.  I’ve spent 45 minutes trying too add my foods for the day and to store foods that I eat regularly so that I don’t do a daily search, and that’s all time that could’ve been spent exercising.  I hope we get an update soon on what’s being done because it’s not a hard thing to fix.

[Spyder215]

I am having similar issues as the others. Some foods register, some only in a certain mealtime and some do not enter at all. I have iPhone 8+

[apschwartz]

Also experiencing the same issue.  Have switched to fitbit.com for data entry.  App does appear to properly display the data entered via the web.

I hope an email goes out to (at least) those posting to this thread when a fix is released.

[MELKUZ]

Mine quit today too 

[CorbinA]

I'm having the same problem on my iPhone X since the app was updated today.  I try to log food items and they will appear for just a flash (a second) and then disappear.  Or, once in a while, it will change to an entirely different item.  I've tried restarting multiple times, but it doesn't help.  So, I'm now unable to use the iPhone app to log my food at all, which is super annoying since I will be travelling for a few days and will only have access to my phone.  I am still able to log food through the website on my laptop, but that's not very convenient.  Please fix the iPhone app!  (Or just let us all revert to the previous version that worked.)

[Giampi71]

Hello @JCSask,

The developers are aware of the issue hitting the iOS app (so it's not a stricly Ionic related issue).You might read the dedicated thread:

https://community.fitbit.com/t5/iOS-App/Issues-with-food-input-on-iOS-2-53/m-p/2825777#M87620

[lal47]

Worked fine all day until dinner tonight .... Now I'm having same problem as others listed here. (iPhone 6S Plus)

[Kayla1989]

This is happening to me as well :@

[CanadaMike]

Same issue. Foods actually change from what is entered (both title and calorie counts). Custom food deduct from remaining calories but do not show up. After restart, they are gone. Something went really bad with this latest update. QA should be all over this.

[Jcrback]

Husband and I both having problem entering foods but only if we have NEVER entered them before.  I had company yesterday and was too busy to enter my dinner foods.  I updated this a.m. And tried to enter today's breakfast entries first and it didn't work and I didn't have time to fool with it. (Once before it acted hinky and I had to power my phone down and reopen app to enter foods).  So tonight , after powering down our iPhones S7 & S8, we tried to enter today's breakfast with no luck.  Called my daughter and she gave me the bad update news.  No one posted what we discovered so here it is.   We've entered some stuff on yesterday's date including my entire dinner last night with no problem even though most items were in our Frequent, recent or custom listings. All we could enter on today's date were brand new items that we had never entered before.  Anything in our Frequent, Recent, or Custom would flash on and then disappear.  Tried adding straight from internet but if it was ever in our Frequent, recent or custom, it went to our old list and showed foods we had listed with the food we pulled up and when we tried to enter that, it flashed and then disappeared.  My husband, oldest daughter, her husband and I are all on your program, since last Thanksgiving.   Our youngest child (the computer geek) is singing the praises of the Apple watch.  Hmmm....

[Jcrback]

Sorry, in my haste I typed my first line incorrectly.  We are only having trouble entering food we have entered before.