02-09-2019
06:37
- last edited on
02-10-2019
06:21
by
LanuzaFitbit
02-09-2019
06:37
- last edited on
02-10-2019
06:21
by
LanuzaFitbit
Charge 2 -22.55.02
Galaxy Siii - Android 4.4.2
Fitbit App Version 2.75.1
I haven't done an app update on my phone in a while and apparently, when I did this about 2 weeks ago it broke the ability for notifications (phone calls, text messages and google calendar alerts) to get pushed to my Charge.
I have tried all the various suggestions on the support page and was online with support for a while last night. The bottom line, she said the current version is not compatible with my phone.
Is there a "roll back" version available?
Thank you.
Moderator edit: Clarified subject
02-10-2019 06:23
02-10-2019 06:23
Welcome to the Forums @SIII_User.
Thanks for sharing your experience and letting us know that you have tried all of the steps and details you got from our support team.
In this case there is no way to go back to a previous version on the app, at least not officially. If you do find a way to get it please know that since it is not official we cannot guarantee that it will be safe nor that the notifications will work in that case.
Feel free to reach out if you have any further questions.
02-10-2019 09:39
02-10-2019 09:39
Nothing has worked.
I tried removing the device from both my phone and computer and reinstalling it.
I tried turning notifications for phone calls, text messages and calendar off and then restarting as per this article:
https://help.fitbit.com/articles/en_US/Help_article/1979
That didn't work.
From the notifications .... (three dots) ion the phone app, you can send a test call notification from your phone to the fitbit. That worked - a notification was sent to my fitbit.
I am getting really frustrated at this. I just want to roll back to the prior version so that I can use the device as I could before. The main reason I purchased this and not another watch type device was the ability to send notifications to my fitbit. It is really not that useful without it.
While I understand this won't be the correct supported version, unless you can tell me that this was a security flaw, there is no reason to lock out many many of your customers.
02-11-2019 10:11
02-11-2019 10:11
Hello @SIII_User.
Thanks for sharing all of those details and steps that you have tried.
I could see that you are in touch with our support team. They should be able to help you determine what is going on or what is the best way to move forward. I'd say that you continue working directly with them.
Let me know if there are any other questions.