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. 

[RosennFlorida]

Thank You so Much!

[RosennFlorida]

I entered my dinner last nite and it logged correctly on my app  on my iphone, but  on my afternoon snack it was not.. So until they get the bug fixed at least we have the other option of logging i guess.

[Zeppray]

 You know what is really sad you all I knew this was an issue when you did that update.   You can’t be that stupid to not notice this problem.  Plus what is taking so long to fix it. No wonder your company is in bad financial shape.  It shows how much you care about iPhone users.  Just might be time to jump ship and every iPhone owner out there Should be thinking the same thing!  Just very upset!!!

[Gretchen821]

VERY frustrated with the issues going on with my Fitbit. We update our app which is designed to FIX problems, and it adds more issues than we had before!  Where is the logic behind this?  The food log this thread is addressing isn’t the only issue. My weight goal doesn’t calculate any loss when I drop weight, I can get up and walk the length of my house and my steps don’t change, the activity log records exercise sporadically and often incorrectly. I could go into detail on all of these issues, but they have all been well documented here and else where in the communities by others, so what is the point?  How many negative posts do you need to fix an issue?  It’s been the greater part of a week already. Get it together Fitbit or you’ll lose your market share to another! 

[Jim58tr]

One of the first principles used in supporting deployed software is this: “when there is a problem, service must be restored”.

You have violated that principal in attempting to continue to fix a problem that is apparently beyond your ability to either staff, troubleshoot, or understand.

Also, you have failed to grasp the impact of this problem on your user community.

As a result of this issue and other issues that I’ve had with your products I will be looking into alternatives.

You have broken the trust that was present between your paying customers and you the company

[DustyMoth]

Wondering when the food entry issue will be fixed on both the ISO app AND the website? I’ve tried using the website to log my food but keep having issues with it on multiple occasions. Eg I tried logging teriyaki chicken wrap but got an error message saying it already exists but when I search for it I can’t find it.

[Ronniebofa]

Good News: Amazon UK are aware of problem and I am getting to return my Blaze bought 16 August 2016 and get full refund which I will put towards a new Apple Watch.  This fiasco has gone on for too long - so pleased with customer care at Amazon; it’s refreshing compared to the lack of care at Fitbit. All the seem to be good at is deleting post that ask sensible questions or are in the least critical.  How long will this post survive?

[Cathydog]

This is getting silly, 5 days to sort the problem is unacceptable. Any idea when it is going to be sorted out. Not being able to log food is a right pain in the arse!!

[Cjs46]

Me too! Still doing it today (15/7) uninstalled app,reinstalled it,made sure it was updated & it’s still doing it!!

If it’s any help I’m using the MyFitnessPal app & syncing it with the Fitbit app.At least it gives you a good idea of your calorie count.

Moderator edit: merged posts

[KrissyKLK]

Yes, this definitely goes down in the first world problem book.  However, it's a popular product that a lot of people have gotten used to and I've learned on here that others depend on it for medical needs (which is cool).  My first post was deleted but again I will ask that they please back out this buggy update.  I was a computer programmer and even with testing understand that things happen.  It's better to just admit it and go back to the original version while you resolve the issue and test and retest.  No one would be upset that you made a mistake. Customer service is 90% of the game.  Communicate. There are over 40 pages of postings about this issue. This is first time I have ever been inclined to go onto this forum. I didn't realize how much I use this product until I couldn't.  I (along with others on here) have been a loyal customer for years.  I LOVE my FitBit.  I'm approaching middle age and in the best shape of my life thanks to FitBit. It's sad that they are ruining the integrity of the product by not just getting us back to the old version while they fix it. 

[SunsetRunner]

Who else thinks this will take as long, if not longer, to fix than the Android version that ate up user data? That took a little over a week. 

I have a new Apple Watch, paired and ready to go. I'm not waiting a week to see if Fitbit fixes this. 

And it's not just the fact that we're on the fifth day of this not working. It's the fact that the company sees fit not to tell us what exactly is happening. It's the fact that we've been told that rolling back to a working version was considered but not done because reasons? It's the fact that, despite this thread gaining several pages by the day, angry posts that are completely valid are being deleted because the moderates are more on top of keeping this thread "clean" than the developers are on top of making sure their app works. 

We're being kept in the dark and not given a working version while the new one is fixed, and for what? 

Gonna sell my Blaze. I'm done with this. 

[KClinard]

Any chance this will not be fixed? Should I get a new app?

[Ronniebofa]

If you bought the Blaze from Amazon less than 2 years ago you can receive a full refund by stating it is not fi for purpose and being misplaced at present as it does not allow you to log food via the app as advertised and described in user manuals.you could approach other vendors with the same argument and see if they will also refund.

[OttoMarr]

I have now stopped using my fitbit Blaze because it has become useless to me.  First the issue that heartbeat and calories burnt were regularly and substantially overstated making the calories gap shown to me totally wrong and unreliable as a tool for my weight management.  Now the calorie intake measuring via the fitbit app on my phone has also become impossible (forget the theoretical possibility of going to my desktop computer for doing that, not practicable....).  There is nothing left to make my bulky fitbit Blaze worthwhile carrying on my wrist.  Just to measure a few steps I’m taking?  No, I have switched back to my beautiful analogue gold watch now, and I’m starting to forget about the fitbit tracking disappointment.  

[YP07]

Thanks for the information I might try that

Sent from my iPhone

[FitCat1973]

I find it interesting that my post was edited to remove the phrase "crappy update".   Fitbit engineers - I am not sure who you think you are fooling.  Everyone who has posted here agrees that your last update was crappy!  Instead of editing posts why don't you fix the problem!  Surely your engineers could use the assistance since it has now been 5 days and the app still does not work properly.  Learn how to run your organization!   

[fireweeds]

I am starting to wonder if I should look for another brand... In general, I really like the options the Fitbit has but haven’t looked at others yet.
I have other problems, though minor, with the food log all along: wouldn’t list numerous foods in its memory that I am logging frequently and I had to re-enter them over and over again, and the app would recalculate retroactively my BPM, changing the values for the previous week.
For now, I’ll likely stay with Fitbit but am starting to look for alternatives.

Interesting! Thank you! Does syncing it keep the food data in the app on the cellphone?

Moderator edit: merged posts

[Holden42]

As a workaround, I've been using the Lose It! app to log food, calories, macronutrients; you can sync it to fitbit so it will show you calories burned on the Lose It app and the calories consumed from the Lose It app. You can barcode scan and search the food database with Lose It as well. MyFitnessPal is another app option.

Would be interested to hear of any other workarounds folks are using. 

[Valentine000]

I’m having the same problem I put my toasted bread down & detox tea & put saved, then it cane up with chicken teaka . That’s not what I had for breakfast. Have reported this but still the same problem. Anyone know why this is happened. 

[guitarwoman]

Need to explain to anyone who thinks I’m whining that I have a Versa, and the problems with it are legion. I gets phantom steps when you are charging it if you have a fan running on the same surface (?) and sleep logging is comical, last night it logged me as awake for half the night. I have to adjust my sleep log almost daily.

And now the food tracking....

I still have the old version of the app because I don’t allow manual updates. I don’t think the iOS update is a problem here, I have the latest version and the food tracking on the older Fitbit app is working fine. For now.

Sent from my iPhone 

Moderator edit: personal info removed