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. 

[Legend58]

This is getting beyond acceptable. I’m going to move to my fitness pal if this is not fixed by Monday. I I don’t understand why you can push out / return to the last working version of your software. Because right now and for the last few days you app has been useless!!!! Get off your .......

[Legend58]

This is getting beyond acceptable. I’m going to move to my fitness pal if this is not fixed by Monday. I don’t understand why you can push out / return to the last working version of your software. Because right now and for the last few days you app has been useless!!!! Get off your .......

[strwelz]

I don't know if this is affecting anyone else, but I am unable to add food for today, 7/15/18 at Fitbit.com.  I try, but it just adds the food to yesterday's log (7/14/18)

[ChrisB_UK]

Yep - been a problem for a week - get the laptop out to do the hard way! It does give more data though which I didn't realise! 

[RickM63]

A suggestion that if everyone rates the APP as 1 (currently a cumulative rating of 3.7) they will soon give us an update. Bet they give us an update before we can drive it below 2. 

Make your voice count! 

[Sh56]

Same issue iOS 11.4.1

[Lwhite70]

Is this food log working yet? Have I missed the solution??

need my food tracker!

[Scratchymon]

Was just thinking the same thing. I’m switching to Verizon and seems like a great reason to drop my Fitbit for an Apple Watch. I liked my Fitbit as I’m a fan of simplicity my Fitbit does (or did) everything I needed it to do.
Sent from my iPhone

[SunsetRunner]

No useless update today Kate?? It’s pretty clear no one has to work sundays at Fitbit no matter what (except whoever is responsible for censoring paying customers) Must be nice. Since you are bent on all of us moving to My Fitness Pal we might as well switch to the Apple Watch as well. Thanks for nothing.

[Scratchymon]

I’ve tried using spark people and my fitness pal today and also the scanner is not working. Perhaps this is an iPhone problem.

Sent from my iPhone

[SunsetRunner]

Fitbit have already confirmed this is not a hack (the Fitbit community people pasted a link on this earlier in the thread.

However if it was they would have a duty of care to inform all users impacted ASAP especially with so much personal data captured by Fitbit.

So I don’t think it is, but that’s nothing more than my opinion so you will have to make your own opinions but based on the info on the threads and earlier assurances from the moderators I think it’s a bug with the app update, which would have been a much larger impact to have rolled back the previous version (for example backend infra changes as well as the app).

It still doesn’t excuse poor release management and testing QA which has obviously failed in this case for something which is a core feature.

I kind of feel for the moderators here as they are the front line to the users and are not the devs  working on the engineering, and will be under instructions from Fitbit on what to say or do but I am sure will be passing up that we are all unhappy (I am using the word unhappy so the moderators don’t dete this post ;)).

Don't get me wrong it’s still a huge pile of quality assurance and release management pants and I am starting to feel drawn to watching the Apple Watch 4 release rumours now!

[Katieloo-65]

My rice last night was apparently a packet of shortie biscuits. Really hope they get this sorted soon 🤞🏻

[Sue50]

Mine is exactly the same, been like this for about 4 days now

[BOTTA]

It’s not iPhone related. Either Fitbit coders screwed up their update trying to keep up to Apple’s upgrade, or something worse happened, like a targeted hack. If it’s a stew up then Fitbit needs to fix it now, if it’s the later....

[Kallioppe]

Wow... It almost feels like they've abandoned funding a solution. Really disappointing.

[DaveMo]

The number of people posting in a discussion like this is always a gross underestimate of the number of people affected.

1. Many people are not aware that this is a general problem (since Fitbit management has seen fit to NOT notify users of this problem), and assume it is just their unit that is defective (and they ARE telling their friends how defective Fitbit is);

2. Many people are not aware that this discussion board exists. Nor should they be - they paid money for a product that should work, and they should not be expected to be aware of discussions like this just to get the product they paid for;

3. Even if aware of this discussion, many feel they shouldn't have to spend even more of their time to get what they paid for. They paid money. They didn't get what they paid for.

You are correct. There are absolutely THOUSANDS of people affected by this. Most are quietly pissed off and spreading the word.

[BOTTA]

I didn’t see any previous comments that it’s not a hack but I really hope it’s not. The way they have tried to downplay this and not give any information is bad. “Looking into this” for a week does not do it me...and as much as I like their software this is reason enough for me to move on if they think I’m waiting another week hearing such a bad excuse for communication and problem resolution.

[KatyW]

What?? Well geez no wonder it’s 3:30 and I’m down to 260 calories left for
the day. Grr. Thanks for the heads-up. This sucks.

[Tripletmom3]

I’m having the same issue. I updated my iPhone software this morning and now my food log will not work! 

[Krissyw]

I am having similar issues - i cant log food correctly at all, i input food and calories and the app wont save them, or input them and the app says its something completely different to what i have eaten, removes calories instead of adding- its all over the place! iphone SE and fitbit blaze.