12-04-2019 15:52 - edited 12-16-2019 14:50
12-04-2019 15:52 - edited 12-16-2019 14:50
Update 12/13/2019: Please ensure you are on the latest iOS version, currently 13.3. Also check out the updated instructions in our notification help article.
This thread is a continuation of our previous discussion on notification issues introduced with iOS 13. If you are experiencing difficulty with your notifications after updating to iOS 13, please carefully follow the steps in this article, which are also documented below.
These steps should resolve the issue when followed correctly. We realize this process can take some time, and encourage you to proceed carefully and deliberately through every step, even if you think you've already done so.
If these steps do not appear to resolve the issue for you, please try them at least once more to be certain, then respond in this thread with specific details about where you were unable to proceed, or what unexpected behavior you are still experiencing.
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 double-check the following:
This feature prevents your phone from sending notifications. Verify that Do Not Disturb is off:
Again, if these steps do not work for you, please try them more than once and then let us know specific details about your experience so that we can assist further. Please keep your app up to data and watch this thread for new information.
What's your favorite healthy breakfast? Share your best recipes and join our discussion!
Actively managing your weight? Find accountability buddies on the Manage Weight board
12-28-2019 08:53
12-28-2019 08:53
I have went through all the steps several times and still not getting any notifications.
12-28-2019 09:07
12-28-2019 09:07
I have tried for several weeks to get my Charge 3 to successfully get notifications from my iPad and iPhone (both running latest IOS 13 update). Prior to IOS 13 I got notifications without any issue.
I am ready to transition to another tracker provider if I am unable to get assistance to solve this issue.
12-28-2019 09:15
12-28-2019 09:15
I think you’re in the wrong help forum, I thought this was iPhone help for Fitbit Charge 3. I think you need to go back into help and click Android.
12-28-2019 09:15
12-28-2019 09:15
Good deal!
12-28-2019 09:17
12-28-2019 09:17
Why so angry? It’s not necessarily Fitbit’s fault. You said yourself it happens every time you do an iOS update. Apple doesn’t play well with others, including Fitbit. Once Apple has an iOS update, you need to be patient with Fitbit so they can do the work when people start having problems.
Did my solution work for you? I see it worked for at least one other person.
12-28-2019
10:07
- last edited on
12-31-2019
09:32
by
EdsonFitbit
12-28-2019
10:07
- last edited on
12-31-2019
09:32
by
EdsonFitbit
I have tried all these steps several times with my new Versa 2. My iPhone XS is updated to the latest iOS 13.3, as is the Fitbit app. I’ve tried countless times to forget the Bluetooth, add the device again on the app, delete the app, to no avail. I’ve tried calling Fitbit and it did not help, they tell me developers are working on it with no eta for when it will be fixed. I had the same problem with my AltaHr that started a couple months ago, thought the new device would change that. Nope! My mother in law has the same phone I do, also the Versa 2 and she gets notifications. What is going on? I used to love my Fitbit, now I’m disappointed and considering returning it for a full refund and get a device that works. Any help would be greatly appreciated.
Moderator edit: format
12-28-2019 11:10
12-28-2019 11:10
I understand that you put this “fix” out here to try and help, but, not only does it not work, it’s pretty insulting to those of us that are pretty tech savvy. “Even if you think you’ve done it, try it again”. Come on now! Don’t make us jump through hoops and still be let down while the developers try to come up with real solution. From what I’ve read, this update isn’t the only one that your users had issues with and for the same reason. You are a big brand and honesty should be your policy. I would have been much happier with a “we know there is an issue and we’re working on it, please be patient” than “try this and waste your time til we figure it out”
I fixed my problem by switching to a different brand.
12-28-2019 11:19
12-28-2019 11:19
It doesn’t matter if Apple doesn’t play nice with FitBit. Fitbit advertises as being compatible. If that’s not the case, they need to make the Apple users aware of it so they can make the call to purchase or not.
12-28-2019 11:24
12-28-2019 11:24
I'm curious why some people are blaming Apple when the issue is that Fitbit takes more of a reactive approach than a proactive one. The changes that come in the ios or android operating systems are known to all the app developers well ahead of time. In this case Apple provided the ios 13 beta 3 months in advance! Many apps worked well when ios 13 was released fibit just wasn't/isn't one of them. I provided this link and if you check the dates you can see that users reported notification issues as early as June 2019 with ios 13! https://community.fitbit.com/t5/iOS-App/Stopped-seeing-notifications-after-updating-to-iOS-13/td-p/3...
I realize not everyone is an app developer and as this is a family oriented website I'll provide some comparisons to what a beta period is.
1. Picture a couple getting engaged. There is no surprise that they are getting married. Then you get those save the dates in the mail about their wedding date. If you planned on going to the wedding wouldn't you plan ahead and make sure you were off work and made any necessary travel plans? Picture the save date as the beta period.
2. The couple got married! Now they are having a baby. Usually there is 9 months notice prior that pretty soon there is going to be a baby. People plan a baby shower and make sure their house is ready for a baby so that they are prepared. That 9 month time frame...it's the beta period!
So is it really Apples fault that they told everyone back in June about the changes coming in September and that not every app developer opted to check their apps? Or that it's just about January and some developers are still having trouble with what happened in September?
12-28-2019 12:19
12-28-2019 12:54
12-28-2019 12:54
Ever since the last update, my tracker got all messed up. And now it doesn't even work.
Thank you Fitbit for wasting my money!
12-28-2019 13:41
12-28-2019 13:41
Got a Blaze. Got an iphone running 13. IOS. Same "vibrating on calls" issue. Love to hear when it's updated.
12-28-2019 13:44
12-28-2019 13:44
Any other options as trying this three times did not resolve the issue.
12-28-2019 14:45
12-28-2019 14:45
Trying to just load fitbit ios on versa light and have tried for 3 days. Will not stay connected nor load downloaded material . have tried 2 different phones
12-28-2019 15:26 - edited 12-28-2019 15:50
12-28-2019 15:26 - edited 12-28-2019 15:50
@SoCalBlaze I'm not really sure we can expect a fix for the blaze vibrating issue. There hasn't been an update to this tracker since like September 2017! I like referring to it as the "forgotten" tracker since it didn't have anywhere near the life cycle of a tracker like the fitbit one or some of the others out there!
I think its kind of odd that this started when others are reporting no notifications. Or that it keeps vibrating for a phone, but not a text message.
I'm not sure if you set the text reminders, but i have mine set to once. My fitbit doesnt vibrate for the 2nd notice on a text.
12-28-2019 15:56
12-28-2019 15:56
Like everyone else, I’ve done everything suggested multiple times. I now only get call notifications. I’m terribly disappointed. How much longer until this is fixed?
12-28-2019 15:58
12-28-2019 15:58
I have tried these steps several times and still not receiving text messages after updating iPhone. Very frustrating!
12-28-2019 17:11
12-28-2019 17:11
Having issues as well, tried everything listed here. Talked to Fitbit on phone today and they did all this again with me. Still not working. They said that someone from Fitbit would send an app update to me, I haven’t gotten anything yet.
12-28-2019 18:27
12-28-2019 18:27
Not working. These steps do not help. Tried plenty of times. I do not receive 90% of notifications including calls and texts. When I make a phone call my blaze vibrates (saying I have an incoming call) when the person I called answers and continues vibrating without being able to silence it. Also notifies me I have an incoming call while on the phone with that person. This is extremely frustrating to still be happening and these are some primary reasons for having my blaze. It’s really starting to piss me off that it has not been fixed yet.
12-28-2019 19:02
12-28-2019 19:02
I get everything but messages. I have done everything on list.