05-11-2016 10:26
05-11-2016 10:26
05-11-2016 15:23
05-11-2016 15:23
Welcome to the forums @Shlomo-T
Same thing with my Android app as well. I'm pretty sure one of the Fitbit moderators will see this and let their tech people know about it.
I thought I was getting overly enthusiastic and cheering, but since it's happening to you, it must be a glitch.
Keep on stepping!
05-11-2016 17:18
05-11-2016 17:18
@Shlomo-T @Odyssey13 Thanks for your feedback! I was able to recreate getting booted off of the Challenge page by clicking on cheer a bunch of times in succession, but to clarify, it didn't boot me out of participating in the Challenge. Did it do that to you? Either way, I've forwarded this information to our Product Specialist team who is looking into this. Thanks again for the feedback, totally appreciated!
05-11-2016 18:24
05-11-2016 18:24
05-11-2016 18:25
05-11-2016 18:25
05-11-2016 18:58
05-11-2016 18:58
@ErickFitbit if I go slow and tap cheer once, it takes several seconds for it to complete the cheer.
Thanks for taking good care of us!
05-11-2016 22:25
05-11-2016 22:25
@ErickFitbit Same here, It does not boot you out of challenge. Just really slow.
Wendy | CA | Moto G6 Android
Want to discuss ways to increase your activity? Visit the Lifestyle Forum
05-12-2016 10:43
05-12-2016 10:43
@Shlomo-T @WendyB @Odyssey13 That's what I also experienced and provided as feedback to our Android team. Thanks for reporting this! When I hear of an update about this, I will make sure to pass it along to you all.
In the meantime, try not to double-tap on the "Cheer" button as it will boot you off the page. Thanks again for the reports!
05-12-2016 19:06
05-12-2016 19:06
05-13-2016 16:02
05-13-2016 16:02
@Shlomo-T Awesome news! Glad to hear that it's been fixed for you and thank you for the update!
05-16-2016 08:19
05-16-2016 08:19
05-16-2016 08:54
05-16-2016 08:54
@ErickFitbit Sorry to have to say this, but @Shlomo-T is right. It started acting up again.
I'm sure that Fitbit will work out this glitch.
05-26-2016 15:45
05-26-2016 15:45
@Shlomo-T @Odyssey13 Thanks for confirming that the bug is still occuring. I've forwarded the information to our Android team who is currently working on getting this resolved. Thanks again for the follow-up!