01-11-2016
05:21
- last edited on
01-16-2016
12:02
by
ErickFitbit
01-11-2016
05:21
- last edited on
01-16-2016
12:02
by
ErickFitbit
Since updating to 2.17, I have been unable to open my Fitbit app on my Droid Maxx (Android 4.x) Each time I try, I get the "app stopped working" message. Is there a fix?
Moderator edit: edited title for clarity
Answered! Go to the Best Answer.
01-11-2016 11:46
01-11-2016 11:46
You have 2 options to fix the problem
1: un-install the app and reinstall, or
2: go into the device settings|application manager, find the Fitbit app, clear both items (cache & data) that are listed.
In either case, you'll need to log back in to the app.
This fixed the problem for me. I used option 2.
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
01-11-2016 06:33
01-11-2016 06:33
I got the same problem since updating to the latest version 2.17. I have HTC One M8. the application is not usable at all. Any news when we can expect a fix
01-11-2016 11:46
01-11-2016 11:46
You have 2 options to fix the problem
1: un-install the app and reinstall, or
2: go into the device settings|application manager, find the Fitbit app, clear both items (cache & data) that are listed.
In either case, you'll need to log back in to the app.
This fixed the problem for me. I used option 2.
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
01-11-2016 13:42 - edited 01-12-2016 12:50
01-11-2016 13:42 - edited 01-12-2016 12:50
Hello,
Yes, option 2 fixed the problem for me as well. Thanks a lot for the help.
01-12-2016 10:39
01-12-2016 10:39
Did those options keep working for you? I'm finding that I have to clear cached data before trying to load the app every single time!
01-12-2016 12:00
01-12-2016 12:00
Yes, option 2 worked for me and seems to be continuing to function. It was clearing all the data that did it. Clearing the cache had no effect for me.
It is still annoying that this happens.
01-16-2016 11:56
01-16-2016 11:56
@gdio53 Thanks for sharing what worked for you!
@tornadogrrrl@JenMah If you do @gdio53's suggestion #2 and then restart your phone immediately after, do you continue to see the same message?