06-16-2016 09:01 - edited 06-29-2016 13:15
06-16-2016 09:01 - edited 06-29-2016 13:15
Fitbit update 06/29/2016: Thanks to everyone who took the time to test the new update and confirm that the "My Foods" tab has been restored with the latest release of the Fitbit app for Android, version 2.28.
As this issue is now resolved, I am closing this thread. If this comes back please create a new thread and use this thread as reference. Again, thanks for all the reports and help in getting this fixed.
Fitbit update 06/28/2016: Hi everyone -- The "My Foods" tab has been resolved with the release of the Fitbit app for Android, version 2.28 update. Please update and let me know if it's been fixed for you.
The issue with crashes when logging custom meals is still being looked into and has not yet been fixed. You can follow the updates for that issue here.
Fitbit Update 06/23/16: Hey all, our team has a fix in place for this bug which should be coming in an upcoming Android app release. I will confirm the date and version of the fix once I have confirmation from the team.
Fitbit Update 06/16/2016: Some community members have reported that since the Android 2.27 update the "My Foods" tab in the Android app has disappeared.
I've made our Android Team aware of this; they are currently working on getting this resolved. When I hear an update from them I will make sure to share it with everyone here. In the meantime, I recommend using the online Dashboard at Fitbit.com if you need to access the information from the "My Foods" tab until we have a fix for this. Thanks for your reports and patience.
06-23-2016 10:32
06-23-2016 10:32
06-23-2016 16:56
06-23-2016 16:56
Fitbit Update 06/23/16: Hey all, our team has a fix in place for this bug which should be coming in an upcoming Android app release. I will confirm the date and version of the fix once I have confirmation from the team.
06-23-2016 17:16
06-23-2016 17:16
06-24-2016 01:33
06-24-2016 01:33
06-24-2016 05:31 - edited 06-24-2016 05:32
06-24-2016 05:31 - edited 06-24-2016 05:32
@ErickFitbit wrote:Fitbit Update 06/23/16: Hey all, our team has a fix in place for this bug which should be coming in an upcoming Android app release. I will confirm the date and version of the fix once I have confirmation from the team.
Erick,
I installed the 2.28 Beta, and the My Foods tab is back, but recording a meal is still broken and crashes the app.
Thanks,
Gary
Gary D.| Feeding Hills, MA MBG PE
Charge HR, Charge 2, Charge 3, Inspire 2, Charge 4, Charge 5, Pixel Watch 2, Pixel Watch 3
06-24-2016 13:39
06-24-2016 13:39
06-27-2016 15:22
06-27-2016 15:22
@gdio53 I recommend sending a crash report when that crashes via the beta app.
06-28-2016 06:19
06-28-2016 06:19
@ErickFitbit wrote:@gdio53 I recommend sending a crash report when that crashes via the beta app.
Erick,
I'vr tried to generate a crash report, but it doesn't complete.
There's another thread where other users have reported this issue, and you've acknowledged the problem
Thanks,
Gary
Gary D.| Feeding Hills, MA MBG PE
Charge HR, Charge 2, Charge 3, Inspire 2, Charge 4, Charge 5, Pixel Watch 2, Pixel Watch 3
06-28-2016 11:32
06-28-2016 11:32
06-28-2016 15:07
06-28-2016 15:07
Fitbit update 06/28/2016: Hi everyone -- The "My Foods" tab has been resolved with the release of the Fitbit app for Android, version 2.28 update. Please update and let me know if it's been fixed for you.
The issue with crashes when logging custom meals is still being looked into and has not yet been fixed. You can follow the updates for that issue here.
06-28-2016 15:34
06-28-2016 15:34
Hi ErickFitBit,
That latest update did the trick, the My Foods tab is back!! Yay!
06-28-2016 17:40
06-28-2016 17:40
06-28-2016 22:26
06-28-2016 22:26
Yes, this update seems to have solved the problem for me. Thank you.
06-29-2016 06:43
06-29-2016 06:43
06-29-2016 13:16
06-29-2016 13:16
Fitbit update 06/29/2016: Thanks to everyone who took the time to test the new update and confirm that the "My Foods" tab has been restored with the latest release of the Fitbit app for Android, version 2.28.
As this issue is now resolved, I am closing this thread. If this comes back please create a new thread and use this thread as reference. Again, thanks for all the reports and help in getting this fixed.