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.
09-23-2019 13:07
09-23-2019 13:07
Yeah I turned banners off too. Previews are on when unlocked but I disabled Face ID as this then was showing the message previews on my lock screen. Without Face ID on. All my text messages are shown on the lock screen without preview and my Fitbit Versa was showing the notifications as before. Temporary fix and works for now.
09-23-2019 13:16
09-23-2019 13:16
Yeah this is incredibly frustrating. I not only updated to ios 13 but also my iphone to an XR. Fresh out of the box and the notifcations for text do not work. Like others here I am not too excited about having people being able to see my messages on my phone. So until there is a fix I'll live with it otherwise hello apple watch.
09-23-2019 13:20
09-23-2019 13:20
Having the same issue...HELP! I tried un-pairing then re-pairing the bluetooth, removing then re-adding my Fitbit in the app, resetting my Fitbit, un-installing then re-installing the app, checking if notifications were turned on in the app AND in my phone's bluetooth menu and NOTHING! Hoping they release an update to fix this ASAP.
09-23-2019 13:25
09-23-2019 13:25
I've had this same issue. I was a Beta Tester on ios13 - and alerted Fitbit multiple times to the issue. The common response was "we don't support beta test... blah blah blah" so it was absolutely a known issue on their end prior to ios13 being released. There were other posters on the message board and in the community that made it known. I emailed as well, and it was all the same standard stuff. So they've been aware of the issue. Just not sure why they wouldn't fix it. It really makes a strong argument to transfer over to the Apple ecosystem, and just get an Apple Watch.
09-23-2019 13:29
09-23-2019 13:29
For me my Fitbit isn’t even syncing. I’ve restarted my iPhone, turned Bluetooth on and off and connected / disconnected etc etc. I’ve literally done it all and it still says Bluetooth isn’t on nor connected, but it is!! Ahh ;-;
09-23-2019 13:39
09-23-2019 13:39
I just upgraded my phone from iPhone 7 to the new 11 pro max last night and the messages (iMessage, Whatsapp and LINE) came through for the evening but noticed that it stopped this morning. I thought I was the only person having this issue but it seems that the problem is with the iOS update..?
Hopefully this gets fixed soon.
09-23-2019 13:53
09-23-2019 13:53
The only way around the problem is to go to settings>notifications>show previews>always
that is the only way to get texts messages up until FitBit release a fix. Doesn’t work with apps like WhatsApp etc though
09-23-2019 14:01
09-23-2019 14:01
Go to settings>notifications>show previews> always
then delete the app and reinstall, turn back on notifications within the Fitbit app.
back in phone settings you can change to “when unlocked” or keep on always and they come through from every app. Just not on never.
hope this helps
09-23-2019 14:51 - last edited on 09-26-2019 18:27 by LiliyaFitbit
09-23-2019 14:51 - last edited on 09-26-2019 18:27 by LiliyaFitbit
thanks, turning on the preview has allowed notifications to come through but I hope you can resolve the issue so that the preview doesn’t have to be switched on. For privacy reasons I don’t like text previews appearing on my phone!!
Moderator edit: format
09-23-2019 14:59
09-23-2019 14:59
That’s still not even allowing texts to show on my versa. I’ll just have to wait until Fitbit fixes the issue
09-23-2019 15:17
09-23-2019 15:17
Quick question. This fix did help me get my messages but I am getting notifications multiple times for my calendar. Like every 30 min or so i keep getting notified of something i was notifies this morning about. Since IOS 13 this has been happening. The event is scheduled for all day but before IOS 13 this did not happen. Are you aware of this issue? Thanks
09-23-2019 15:28
09-23-2019 15:28
We tried the fixes and still no text notifications
09-23-2019 16:13
09-23-2019 16:13
Got my calendar and audio call notifications to work, but still no text notifications.....
09-23-2019 18:25
09-23-2019 18:25
This “fix” is what finally worked for me. But I definitely dislike having to show message previews.
09-23-2019 18:53
09-23-2019 18:53
Hello @phouse I've moved your iOS question out of the Ionic hardware support.
Please see the pinned post on your issue at the top of the iOS board.
The issue is in the changes iOS made to notifications and Fitbit is working on a resolution.
09-23-2019 19:01
09-23-2019 19:01
Where is that setting?
09-23-2019 19:13 - last edited on 09-26-2019 18:29 by LiliyaFitbit
09-23-2019 19:13 - last edited on 09-26-2019 18:29 by LiliyaFitbit
Nope, didn’t work. I went through this on the last iOS update, and then Fitbit came out with an update in the app and it fixed it. There hasn’t been a new Fitbit app updates since I got the iOS 13
Best Regards,
Moderator edit: personal info removed
09-23-2019 19:29
09-23-2019 19:29
I did all the same things with no luck. I hope this gets fixed soon because I am missing texts all day long now. Everything else works fine
09-23-2019 19:35
09-23-2019 19:35
We found it under settings: notifications and have to set previews to always. We also went into Bluetooth settings, clicked the “i” beside his versa and toggled the switch off and on. He now receives notifications when he isn’t looking at the phone.
09-23-2019 21:18
09-23-2019 21:18
I'm having this same issue. Just started today. I tried all the trouble shooting steps, but nothing seems to work.