05-23-2016 15:36 - edited 06-07-2016 10:53
05-23-2016 15:36 - edited 06-07-2016 10:53
Fitbit Update 06/07/2016: As this issue has been resolved, I am closing this thread. If you experience instances of crashing when clicking on "Alarms" in the menu on the Android app, please create a new post and reference this thread so I can look into it once again.
Thank you to everyone who reported this issue.
Fitbit Update 06/02/2016: We've just released an update for the Fitbit App for Android, version 2.26 which should resolve the alarm crash issue for everyone.
Please update your app and let me know if it's fixed the issue for you. Thank you!
Fitbit Update 06/01/2016: Hey everyone -- We're in the process of releasing an app update that should resolve the alarms crashes that you're experiencing. The app release is going out in increments so you may not see it available yet, but I will keep you all updated once it's been released to everyone.
Check the Google Play Store for available updates to the Fitbit App for Android and make sure to complete the update.
Fitbit Update 05/25/2016: Good news everyone! We have a fix in place for this crash which should be coming real soon! Thanks to everyone who was super helpful in giving me your device and OS information so our engineers could further investigate.
When I have a solid date and app version which this fix will be released in, I will make sure to provide you all with another update. Again, thank you for your patience and help!
Fitbit Update 05/23/2016: Some users who have multiple trackers paired to a single account have reported when they click on "Alarms" in the Android app, version 2.25, the app crashes.
Our team is currently looking into these reports and would love your help with a couple of questions, if this is happening to you:
Also, as a temporary workaround I recommend setting and adjusting your alarms via the online Dashboard under the "Device Settings" page.
As I hear further updates on when this will be fixed on the app, I will make sure to provide you all with updates here. Thanks for the reports, and check back here as more to follow soon.
05-21-2016 18:51
05-21-2016 18:51
05-21-2016 18:57
05-21-2016 18:57
05-23-2016 06:22
05-23-2016 06:22
05-23-2016 07:03
05-23-2016 07:03
Strange let me say... I'd recommend doing the following:
Hope that helps my friend, welcome aboard @babylittleoneyo !
Was my post helpful? Give it a thumbs up to show your appreciation! Of course, if this was the answer you were looking for, don't forget to make it the Best Answer! Als...
05-23-2016 07:58
05-23-2016 07:58
05-23-2016 08:04
05-23-2016 08:04
Have you checked that your Fitbit app is running the latest version already? Check it and try it again... in case that this doesn't work I'd suggest setting your alarms via the Dashboard online, but always let me know so I can further investigate about this.
Hope the tip works!
Was my post helpful? Give it a thumbs up to show your appreciation! Of course, if this was the answer you were looking for, don't forget to make it the Best Answer! Als...
05-23-2016 11:29
05-23-2016 11:29
05-23-2016 12:04
05-23-2016 12:04
05-23-2016 14:50
05-23-2016 14:50
05-23-2016 15:32 - edited 05-23-2016 16:31
05-23-2016 15:32 - edited 05-23-2016 16:31
@Lkeeling Do you have the screenshot that displays what Android OS version you're running? Check out my instructions here for where to find it.
@SunsetRunner @Audiobookworm @Katedraper84 @Odyssey13 I've merged your posts into this thread. Check out my previous post for further updates on this issue.
Thanks for taking the time to report this! Hope to have new updates soon.
05-23-2016 16:31
05-23-2016 16:31
05-23-2016 21:32
05-23-2016 21:32
05-23-2016 22:31
05-23-2016 22:31
05-24-2016 03:51
05-24-2016 03:51
05-24-2016 03:52
05-24-2016 03:52
05-24-2016 12:38
05-24-2016 12:38
I just want to say that I recently added a ChargeHR to my account to where I only had a One before. It was after that thhe alarms would not let me access them on my mobile device. Concurrently, I could not access the alarms again until I removed one of the devices (in this case, it was the One again). This makes me think that the app cannot handle alarms with multiple devices.
05-24-2016 13:45
05-24-2016 13:45
05-24-2016 19:57
05-24-2016 19:57
05-24-2016 19:59
05-24-2016 19:59
05-24-2016 22:18
05-24-2016 22:18