09-22-2019 17:46 - edited 10-10-2019 18:22
09-22-2019 17:46 - edited 10-10-2019 18:22
We are aware of an issue preventing some users from receiving notifications on their iPhone after updating to iOS 13. If you're having trouble receiving notifications and you updated your iPhone or iPad to iOS 13, follow the steps in this article, which are also documented below:
App | Settings |
---|---|
Calendar |
|
Messages |
|
Phone |
|
All other apps |
|
For instructions, see the Apple help article.
If these steps do not resolve the issue for you, please keep your app up to date, and watch this thread for new information. We apologize for the inconvenience and appreciate your patience while our team works to address this.
Answered! Go to the Best Answer.
10-14-2019 09:31
10-14-2019 09:31
This latest debacle is the final straw for me. I'm going to be shopping for an Apple Watch soon. When the holiday sales come out, I'm buying one and chucking Fitbit to the weeds. It's always something with you guys. Notifications are ALWAYS an issue. Never consistent. You really need to test and troubleshoot your devices way longer before rolling them out. And any time I call FBit customer service, in whatever 3rd world country they work in, they don't know doodoo about anything. My Versa is generally okay, but now another notifications snafu? Come on! For 200 bucks, you really need your product to work consistently. I already have an Iphone and Ipad. Might as well just marry both to an Apple Watch and be able to talk/text from my wrist. I know nobody that's having trouble with their Apple Watch.
See ya later Fitbit gators!
10-14-2019 09:32 - edited 10-14-2019 09:35
10-14-2019 09:32 - edited 10-14-2019 09:35
Good afternoon,
I have tried every step on iPhone and Versa to start receiving text notifications again but nothing seems to be fixing the issue. I can receive calls and the versa will vibrate but will not show any text or calendar notifications. I understand that you’re working on issue after Update and wondering if anything has been resolved yet or if there is any other fix I can try. Again, I have tried every fix that was posted or I looked up & is not resolving the text notification issue. Thanks for the help!
10-14-2019 09:32
10-14-2019 09:32
Nope, and I'm ready to buy an Apple Watch, fo- shizzle.
10-14-2019 09:36
10-14-2019 09:36
No, I still can’t receive text notifications.
10-14-2019 09:43
10-14-2019 09:43
Tried every suggestion and nothing!
10-14-2019 10:27
10-14-2019 10:27
Thank you. I’m going to give them a call
10-14-2019 10:41
10-14-2019 10:41
I tried Fitbit’s solution multiple times and it did not work. Someone else posted this solution below.....it worked for my Inspire :
“
I have the Charge 3 and my wife has the Versa 2. There was only one way for me to receive txt messages with the iOS13 updated. Both of us have the iPhone 8+.
Step 1: Turn off Bluetooth on your phone
Step 2: Delete the fitbit app. All of the data will save from your initial setup.
Step 3: Turn off your phone for 1 minute.
Step 4: Re-download the fitbit app.
Step 5 Turn on Bluetooth and login to the fitbit app
Step 6: Check to make sure:
*Setting - Notifications - Fitbit for "Allow Noticiations. "All alerts on" Options should have "Show Previous 'When Unlocked"
*Fitbit app - top left icon - select your device - notification - txt msg.”
10-14-2019 10:51
10-14-2019 10:51
Yes its really annoying that have to have the preview on my phone as work in an environment where i cant show my messages. That was kinda the point i had the fitbit to start with !!!
10-14-2019 11:02
10-14-2019 11:02
I am using Android and my Versa has stopped giving my text and phone call notifications? I keep seeing the message to apple users but what about us Android users? Very frustrating as I rely on my notifications for work. I have tried restarting and doing everything that has been suggested and still nothing.
10-14-2019 11:10
10-14-2019 11:10
I followed these instructions, get phone notifications but do not get message or calendar notifications. I am very frustrated as I just purchased this fitbit Versa.
10-14-2019 11:50
10-14-2019 11:50
My iPhone updated on 10/9. It has not updated to UHC Motion since then. I’m not receiving any notifications at all. I have a charge 2 that is only a year old! I tried the steps to fix it, but it still isn’t working! Help please, I’m losing my step payments
10-14-2019 11:55
10-14-2019 11:55
Great news, Fitbit just did a new update today and yeah everything is running as normal again. Thanks Fitbit.
10-14-2019 12:03
10-14-2019 12:03
I sympathise with all these messages - I've been using my fitbit Alta for years with no problems until my iPhone updated to ios13 some weeks ago - Bluetooth no longer recognises my fitbit therefore nothing syncs! Very frustrated! I wonder if this is just typical of Apple resulting in another device of theirs having to be purchased or if Fitbit need to get their act together. I don't know what the answer is but I am very annoyed.
10-14-2019 12:05
10-14-2019 12:05
Is there an eta on when this will be fixed? Any updates?
thanks
10-14-2019 12:20
10-14-2019 12:20
I just did the new updated on the Fitbit in hopes that it would correct the problem and still unable to get messages on my Fitbit even after following at these instructions after all updates.
10-14-2019 12:25
10-14-2019 12:25
Any progress with the compatibility issue? I have followed all your steps and my versa will still not sync my text messages from my iPhone but I am able to receive calendar updates.
10-14-2019 12:39
10-14-2019 12:39
I just tried to call. No luck. There is a recording saying they are having technical difficulties and you can go to their website but I cannot understand the website name. Ugh 😡
10-14-2019 12:41
10-14-2019 12:41
I have not and have spent endless hours trying to figure it out.
10-14-2019 12:47
10-14-2019 12:47
10-14-2019 13:32
10-14-2019 13:32
have tried all the info that has been provided and I too am unable to get texts or ring notices on my Inspire HR. Kind of wished I would never have spent the money after reading that Fitbit is not doing anything to correct the issue for over a month - when will this be addressed?