11-07-2019
09:00
- last edited on
11-11-2019
14:28
by
LizzyFitbit
11-07-2019
09:00
- last edited on
11-11-2019
14:28
by
LizzyFitbit
I updated my versa yesterday. Use it with a huawei p10 and now it wont show notifications or calls? I have unpaired and restarted phone then re-paired it . Cleared the cache. Turned bluetooth off and on and again
And it still wont work.
Please help?
Moderator edit: updated subject for clarity
11-08-2019 09:16
11-08-2019 09:16
Hi @CristincaVochot. Welcome to the Community Forums.
Thanks for sharing the issues experienced with the notifications and the steps tried prior posting. I've confirmed that your Huawei P10 is a compatible device, so let's work on this together. Since you've updated your Versa, may I know if the notifications are configured correctly on your watch? You can verify this by swiping down on your Versa, tapping the quick settings icon and turning off the Do Not Disturb (little circle icon) and Sleep Mode (moon icon) options.
Then, try the following steps:
Let me know how everything goes.
11-09-2019 00:17
11-09-2019 00:17
Thank you, but it still not working.😏
11-09-2019 02:51
11-09-2019 03:50
11-09-2019 03:50
Following. Mine has been doing the same thing for two days now. 😠
11-11-2019 15:26
11-11-2019 15:26
Hi @CristincaVochot. I'm glad to see you here again and thanks for the screenshots provided. @AMTGUNT, welcome on board. I'm sorry for my delayed response.
I appreciate your efforts in trying the steps posted above. Our team has received feedback about that error message showing up on the Fitbit app and they're currently working to identify a resolution as quickly as possible. While there isn't a time frame for a fix, I'll update this thread once I have more details. Be sure that your comments will be passed along and don't hesitate to let me know if you have any other question.
See you around.
11-12-2019 01:24
11-12-2019 01:24
Hi,
Even I am facing same issue, showing same error message on my mobile app.
11-14-2019 18:19
11-14-2019 18:19
Hi @Prajwal_kammar. Welcome on board.
Thanks for sharing that you're having the same issue with the Fitbit app. Our team is aware that some of our users are getting this error message and they're working hard to resolve it as fast as possible. Currently there isn't a time frame for the fix, but be sure that this hasn't gone forgotten and once I have more details I'll update this thread.
If you have another question, feel free to reply back.