RESOLVED 07/18/16: App crashes when logging custom meals

[ErickFitbit]

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.

[NalliG]

Hi

Since updating to the latest Andriod app v.2.26, the app on my Samsung S5 it keeps crashing when I try to add custom meals. I get a black screen and a message Fitbit has stopped. I have noticed that the list of custom foods now has food items I have added which did not appear here before. These single food items load ok, it is the meals with multiple food items that cause the crash. I have tried uninstalling and reinstalling the app but the problem is still occurs. No problems with adding these meals on Windows version on my computer.

Moderator edit: edited title for clarity

[mpower9]

---

@NalliG wrote:

Hi

Since updating to the latest Andriod app v.2.26, the app on my Samsung S5 it keeps crashing when I try to add custom meals. I get a black screen and a message Fitbit has stopped. I have noticed that the list of custom foods now has food items I have added which did not appear here before. These single food items load ok, it is the meals with multiple food items that cause the crash. I have tried uninstalling and reinstalling the app but the problem is still occurs. No problems with adding these meals on Windows version on my computer.

---

I have the same problem on my Samsung Galaxy Note 2 running Android 4.4.2. It started yesterday when I updated to Fitbit app v.2.26. 

Yesterday I installed the app on my brand new Samsung Galaxy Tab S2 running Android 6.0.1. I have the same sort of behavior when trying to add a custom meal. The screen went dark, an error message popped up, the screen cleared, and the app was still open and I could continue as usual by entering food items one at a time.

[crippstar]

Since the latest app update today, when I go to log a meal in the Android app (Custom tab), the meal shows as 0 calories. Choose Log This or Log and Add More and the screen goes black, then get message Unfortunately Fitbit has Stopped. Works fine on the dashboard - I can log meals there. Also logging custom food (not a meal) works OK in the app. Problem seems to be just with logging meals in Android app. Tried logging out and back in, forcing stop, reboot, even re-install, all with no luck. Looks very much like a bug in the app - hopefully will be fixed soon.

Anyone else getting same problem?

[jacksondog]

Same exact issue for me on Nexus 5. Started after last update. Reinstall doesn't work. Clear cache and data doesn't work. Meals available through dashboard but showing 0 cal in mobile app.

[mnierman]

Exact same problem on my S6

[jacksondog]

Same issue with Nexus 5.

[Matt_Swatton]

Same problem on Samsung J7

[ErickFitbit]

@NalliG @mpower9 @mnierman @jacksondog @Matt_Swatton Thank you for the detailed report, I've forwarded this information to our Product Specialist Team who is currently looking into this. When I receive an update, I will make sure to update you here. Again, thank you for the time to report this.

[mpower9]

Thanks, Erick

[ErickFitbit]

@NalliG @mpower9 @mnierman @jacksondog @Matt_Swatton To follow-up, can you all please answer the following questions:

1.  Which handset model and OS version are you using (Android 5.1, Android 6.0, etc)? You can use this tool to find out!
2. Is this happening when you are creating a custom meal or only when logging an existing custom meal?

As a workaround for now, you can log custom meals from the online Dashboard. Again, thanks for you help everyone!

[mnierman]

Erick,
I am using SM-920V Samsung s6. It is only happening when logging an existing created meal. Here is my reference number for a chat I did this morning. 11281638
Mnierman
Mike

[Erisari]

Hi there. I am having this issue on my Samsung Galaxy S4. I am unable to log any custom meals into the log on the android app. It shows 0 calories for the meal and when I click "Log This" the screen goes black and pop up shows that "Unfortunately, Fitbit has stopped." I click OK and must restart the app.

Android 5.0.1

Fitbit App Version 2.26 (2182984)

[jacksondog]

Nexus 5 Android 6.01. Happens when logging existing meal.

[jodyboyle05]

Erick,
I'd like to note the same problem with my Samsung A3. Android 5.0.2 Lollipop, Device Code SM-A300FU.
Regards,
Jody.

[NalliG]

Hi ErickFitbit
I am using Android 5 Lollipop. The crash happens when I try to load an
existing custom meal. Thanks for looking into this.
NalliG

[Morbius]

I suggest everyone contact and log an issue with fitbit support. I did two days ago and am getting the automated run around. This isn't going to get resolved in the community boards, only thru logging issues with support. they introduced some kind of bug or database issue when they did the update last week. 

[ErickFitbit]

@mnierman @Erisari @jacksondog Thank you so much for sharing your info! I am forwarding this to our team investigating this. You're the best!

@jodyboyle05 Is this happening when you are creating a custom meal or only when logging an existing custom meal?

@NalliG Which handset model are you using?

@Morbius I am actually working with the Product Specialist who deals with the engineers who work directly with this feature and am forwarding this information to them so they can further investigate. Do you mind helping? If so, please answer the following questions:

1.  Which handset model and OS version are you using (Android 5.1, Android 6.0, etc)? You can use this tool to find out!
2. Is this happening when you are creating a custom meal or only when logging an existing custom meal?

Thanks in advance!

[jodyboyle05]

I've only noticed it when logging a custom meal, I haven't created a new custom meal since the update. The handset I'm using is a Samsung A3, Android 5.0.2 Lollipop, Device Code SM-A300FU.


Sent from Outlook

[Morbius]

I have the same hand set and am running the same version of Android as before the June 2 application update: Samsung Galaxy S7 Model SM-G935A, Android 6.0.1. This phone and Android version worked fine before your June 2 update. I use this feature multiple times a day and being told to go login to the web based version and use that is not a viable alternative.

• This is not a problem with single food item custom meals- only with custom meals that contain more than one food.
• You cannot create a custom meal with more than one food in the mobile app. (normal as before)
• You can only create the meal with more than one food in the web based app (normal as before)
• But you have always been able to log the custom meal in the mobile app. (broken since June 2)
• You can create a single food item custom food in the mobile app and log it successfully. (normal as before)

I have 

• Uninstalled the Fitbit App
• Restarted the phone
• Reinstalled the Fitbit App
• Logged in into my account
• Tried to log a custom meal that has more than one food

When attempting to log the custom meal, the screen goes blank after a moment and the system force closes the application.

In addition, I have edited a custom meal in the web based version (I deleted an item from the meal, I added another item to the meal, saved it) and the same error occurs when attempting to log the custom meal in the mobile app. I have also created a new custom meal with more than one food item via the web based app, saved it and tried to log it from the mobile app. The same error occurs.

I used to read other member/users issues with a grain of salt thinking most were attributable to user issues. However over the last 12 months, every update to the mobile app has made it laggier and more problematic. It takes longer than ever to sync fitbit devices. I get more and more cant connect to fitbit to sync errors as well as tracker not found errors that i used to never get. While it may not be a big deal to some, it is for those of us who maintain our food logs and rely on it to not have to add dozens of foods individually. I feel this food item issue is almost a last straw.

Moderator edit: format