Android Oreo on Pixel: App crashing when logging Food

[AlessFitbit]

Fitbit Update: 9/12/17

Hey, everyone! This issue has now been resolved with the release of the Fitbit for Android app version 2.57. Please update your apps to the latest version! Now that this issue has been resolved, I'm going to close this thread from further discussion. As always, please open a new thread if you come across any new issues. Thanks for your help! 

---

Hi, Pixel phone users! 

Thanks for reporting this app crash on Pixel phones with the new Oreo (8.0) Android update. The app is crashing when manually logging new foods in the app. This has been escalated to our team for investigation. Please stay tuned for any updates! 

[SunsetRunner]

Having the same issue! Pixel XL and Blaze. I'm going through Chemo right now awaiting surgery have to track everything. This is making things harder. Hopefully fixed soon.

[Jyapapaya]

Yes, it says the Google pixel is a supported device. As far as I can tell, all issues have been related to the latest Android update, Android 8.0 Oreo. Before the update, the Fitbit app functioned perfectly on my phone. I believe that Google phones like the Pixel and Nexus get that update first, which is why this issue is popping up with those phones first.

[MarreFitbit]

You're right @Jyapapaya. The Fitbit app does not support beta versions of the Android OS. This is why you're experiencing crashes.

I recommend using Android 7.0 or below or syncing via a computer for the time-being until Android 8.0 is no longer in beta.

Thanks for your understanding with this matter! 

[tannmann]

Android 8.0 is not beta. It was released by Google over a month ago. My
phone received the Android 8.0 update from Google via OTA update. I don't
have any beta software on my pixel.

[Jyapapaya]

Ditto @tannmann. Android 8.0 is no longer in beta. And to be honest I'm getting pretty frustrated that multiple representatives from Fitbit support have blamed the beta version, and not acknowledged that this is an issue that need to be remedied ASAP. 

[hbl2017]

I'm having the exact same problem ...  I have a Google Pixel, Oreo update, and a Charge HR.  Can't search food to add calories because the app crashes EVERY TIME, but I can scan barcodes.  

[Blondy939]

Is there anything else to do? I tried and it still won't work

[Mlrpsyd]

I'm having the same problem, and only since the Oreo update. Is Fitbit planning to fix this? I imagine more Android users will have the same problems once they release the update to more than just Pixel users.

[Jyapapaya]

@MarreFitbit Android Oreo was officially released August 21st. 

https://en.m.wikipedia.org/wiki/Android_Oreo

[AlessFitbit]

Hi, Pixel phone users! 

Thanks for reporting this app crash on Pixel phones with the new Oreo (8.0) Android update. The app is crashing when manually logging new foods in the app. This has been escalated to our team for investigation. Please stay tuned for any updates! 

[SunsetRunner]

And that this problem was reported several months ago during the beta period and Fitbit employees seem to be un-aware still.

[Kitanaor]

Woo hoo!!  I got a Fitbit update last night and it doesn't crash when I log a new food!!!  😀

[Jyapapaya]

@AlessFitbit thank you, and also want to note that when the app crashes it also seems to disable notifications until they are manually enabled again.

[Doubled66]

Everytime I search and try and log food the app closes. It just started doing this, it's kind of difficult to track calories when it closes Everytime you try and log food. How can I fix this?

[AlessFitbit]

@Kitanaor That's great news! Thanks for confirming the latest version of the Fitbit app has resolved the app crash when logging food. 

Hey, everyone! This issue has now been resolved with the release of the Fitbit for Android app version 2.57. Please update your apps to the latest version! Now that this issue has been resolved, I'm going to close this thread from further discussion. As always, please open a new thread if you come across any new issues. Thanks for your help!