09-22-2019 08:38
09-22-2019 08:38
Like a few people on here, all of a sudden my Versa has stopped receiving all notifications except calls. It may work once then it'll just stop. Facebook Messenger, Mood Text messages, Amazon, all were working absolutely fine yesterday. Yesterday I updated the Fitbit app and that seems to be when notifications stopped.
Come on Fitbit, you charge enough for this hardware, can you please stop breaking it?
And don't try the usual "have you checked phone compatibility" line. The compatible phones you have listed are just ridiculous. How can the S10 and S10+ not be listed as compatible when the S9 is? They're essentially the same phone. And as previously stated, all notifications were working 100% perfectly until.the latest Fitbit app update.
Any ideas on a fix this time?
09-22-2019 12:18
09-22-2019 12:18
Only getting text messages and phone calls after last app update. All my phone settings are correct. I have android 9
09-22-2019 15:05
09-22-2019 15:05
I've managed to sort it. I THINK. It was working a few hours ago anyway.
I had to go into the phone settings, Apps, Fitbit, Storage, and delete the cache and data. Reopening Fitbit required me to log in again.
Then had to mess about re-enabling permissions in the Fitbit app when it asked for them, and had to set up all the notifications again from scratch.
Shouldn't have to jump through these hoops though. I'm fairly tech savvy, and it was a pain in my butt to sort out. If someone hasn't got a clue then this could drive them away from Fitbit.
09-23-2019 08:09
09-23-2019 08:09
This worked for me, Thanks! Definitely should not have to do all this after an update but at lease its working now.
09-23-2019 08:44
09-23-2019 08:44
For me uninstalling and reinstalling the Fitbit app on my Samsung S10 and then going through enabling notifications again for every app seemed to resolve this type of issue. For me on my S10, the whatsapp notifications suddenly stopped working but they are working good after this reinstall of the Fitbit app on my phone.
Hope this helps. Ideally Fitbit should have QA'd the recent update but seems they made some boo boos.
09-23-2019 10:12
09-23-2019 10:12
This worked for me! Thank you for the "fix". Hopefully Fitbit will address this in their next update.