Community Moderator Alumni are previous members of the Moderation Team, which ensures conversations are friendly, factual, and on-topic. Moderators are here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
Fitbit Update 07/18/2016: With the latest version of the Fitbit app for Android, version 2.29, the app no longer crashes when logging custom meals.
As this issue has been resolved, I am closing this thread. If you begin experiencing app crashes when attempting to log custom meals please create a new post and reference this thread.
If you're experiencing the issue where you're "missing calorie info when logging custom meals," I recommend checking out this thread for updates.
Fitbit Update 06/17/2016: Community members have reported that the Android app crashes when attempting to log custom meals via the app.
In the meantime, I recommend using our online Dashboard at Fitbit.com to log custom meals until further notice of a fix for this in the app.
I've made our Android team aware of this and they are currently working on getting this issue resolved. When I hear an update on the status of this issue, I will make sure to let everyone here know what I hear. Thanks for your reports and continued patience.
Answered! Go to the Best Answer.
Community Moderator Alumni are previous members of the Moderation Team, which ensures conversations are friendly, factual, and on-topic. Moderators are here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
@jodyboyle05 @Morbius Thanks for confirming when it is occuring for you and for the detailed description of your experience. Our team is currently investigating the issue and I will provide updates when I get them for you guys here.
Best Answer
Best AnswerHaving same problem on Samsung Galaxy S6. Android version 6.0.1
When I try to log a pre-existing custom meal through the Fitbit app, it crashes.
I tap the icon to log food, select "custom", select the meal. I get to the screen that displays the meal name and allows me to select the time/date of the mea.
I click Log this, screen freezes momentarily, then goes black, and I get "Unfortunately, Fitbit has stopped", with options to Report or Ok. The app then restarts, without the meal being added.
Haven't tried to create a custom meal from the app.
Best AnswerSame problem on Samsung Galaxy Note 4 for AT&T (SAMSUNG-SM-N910A) running Android version 5.11 patched to 2016-05-01. I have tried logging out & back in on phone & web, restarting phone, and uninstalling & reinstalling the Android app. Same behavior as others are seeing, i.e. problem occurs consistently when attempting to log an existing multi-food custom meal entry in the Android app. The same meal can be logged successfully in a web browser. Logging custom-entered single foods in Android works fine.
Best AnswerSame issue here with version 2.26.
Try to log an exisiting custom meal, Shows 0 Calories and crashes app when you log.
I un-installed and went back to 2.25. It works fine. (I also unchecked auto updates as well for now.)
Best AnswerDavid88, can you explain how to revert to 2.25?
Thanks!
Best AnswerOn Android
Uninstall fitbit
Uncheck auto updates
Use google to find the fitbit 2.25 apk
Install old apk at your own risk
Reconfigure Login Info and Other Settings
Best AnswerWell, I was hoping the 2.27 update overnight/this morning would have been a fix for this issue, but it's still doing the same exact thing.
Best Answeri had the same thing, basically its now useless. In the description it all looks fine but if you otice when you hit it to add it to say breakfast, it actaully says zero calories. Ive called the customer service they have no idea why. Dont bother trying to create a new one on the computer because that doesnt sync. I have the same phone and this happened after the update. I went into the computer and deleted the custom since i cant use it anyways. Also now the foods list ont he app is gone. leaving me with three, recent frequent and custom.
yes same problem since updating app. I have called twice on this now and they have no clue. You can add it from the computer. Every time they "update" they make it worse. They should just leave it alone. Im starting to hate even using the app.
Best AnswerI've raised it as a support call, they say they've passed it to their engineering teams for further investigation. We'll see. Guess if we all keep chasing it they may do something.
Best Answerim glad you agree too! i called support they are useless as well,the said and i quote "maybe they did away with it to make more space" i hope he heard my head shake through the phone for that stupid response. I wish they would leave the app alone. It was fine three months ago, im not sure what else they need to have it, they covered all the essential items. I thought perhaps you should be able to add a food to favorite like you can on the computer but instead doing away with the whole list in itself is just stupid. BRING IT BACK!
Best AnswerOn the app, the custom food calories show correctly on the custom food list. However when you select a custom food the calories show as 0 and the app crashes when you try to add it.
The Favourite food list has also disappeared from the app.
Now for the web site. When clicking the ‘My Profile’ link I see my profile summary which I share with others. The ‘Last 30 day’ activity graph shows the average daily calorie burn and the average daily calorie intake. The intake value is now showing as 0.
I doubt either have anything to do with the phone or android version. They look like good old bugs introduced by the developers and not picked up by QA.
I'm back to using the web site to log food when I get home which is a major pain. The profile graph is a useful tool, please fix it. Thanks
Best Answer
Community Moderator Alumni are previous members of the Moderation Team, which ensures conversations are friendly, factual, and on-topic. Moderators are here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
@LosingItFast @AleeceH @David88 @vixx24 @Morbius @mnierman @RickyS We just released an app update, version 2.27. Can you all confirm that you've updated to the latest app version and let me know if the issue persists on the latest build? Thank you in advance!
Best AnswerYes, issue persists with 2.27. Nexus 5 Android 6.01.
Best Answer
Best Answer