Incoming call notification continues after the call is answered or ended

[ShazzaD]

I don't know if anyone else is experiencing this, but when I have a call coming in, blaze keeps notifying even after I have answered the call or the caller has rung off. This happened recently, where my phone was on silent. I got a notification from Blaze that I had an incoming call, so I picked up my phone to answer, but the caller had already rung off and the blaze was still notifying me. This has happened a few times now, which is pretty annoying. Is this something FitBit are aware of? and why does it happen?

[MWilli13]

Nope:/

M & K Williamson

[Ashraf.S]

Same here

[Kelly747]

It’s your software that is not compatible with apple, until it is updated, none of your advice will work.  

[alexxicle]

same issue happening to me after updating to iOS 13 too

[SusieHayes]

I am having the same issue with this update!

[Piratesmama]

I’m having the same issue on Fitbit blaze after upgrading to ios13. 😞

[Valerie1214]

I’m experiencing the same issues after iOS update to 13. How much longer will this issue last. Fitbit Blaze

[mvan231]

I have had to turn off notifications on my Blaze because of this issue. It's annoying to answer the phone and have my wrist buzzing away. This seems to be an issue with the new iOS 13 notification system and the way Fitbit notification integration is working together. 

when you answer the call, the Fitbit Blaze screen looks strange too. The answer button slides off the screen but you can barely see the green outline from it. The reject / decline button is gone and the name of the caller is shifted from where it should be. 

[Spider_73]

I’ve been having the same problem since the update to iOS 13. I have a iPhone 8+. I also cannot answer the call through my watch since the answer button has disappeared. It only shows an incoming call or active call. I also don’t receive incoming message notifications anymore 

[MWilli13]

It's not just iOS either.. It's android as well...

M Williamson

[popsw]

Same problem here.  Started as soon as I updated to iOS 13.1 last week.  I don't think mine is intermittent; seems to be every call.  Also, yesterday I was making an outgoing call and it was vibrating and showing on my notification as an incoming call from the same number.  Strange and annoying.

[KLeBlazeS5]

I have a Samsung S5 and was having notification and sync problems of many kinds.

Since I turned off Bluetooth Classic on the Blaze and unpaired that from the phone just using normal Bluetooth, my call notifications don't delay anymore like they did.

[Anna_lynn18]

I’m having the same issue since I received an update with IOS 13 yesterday. Are you still having the problem? 

[Spider_73]

Yes, I’m still having the same problem. The fixes posted on this forum do not work. It’s up to Fitbit to send us a new fix.

Sent from my iPhone

[Piratesmama]

Yes, this is still an issue for IOS 13

[Anna_lynn18]

They didn’t work for me either but it is starting to get annoying

[Lotsaballz]

This was happening to me as well. I corrected in by:

Turn off all Blaze notifications you currently have on

Sync

Turn  Blaze notifications back on

Sync.

This corrected it... hopefully works for you.

[Piratesmama]

This didn't work for me.

[popsw]

Didn't work for me either, but thanks for the suggestion.

[popsw]

Also--there is a notification that indicates fitbit is aware of this and has provided troubleshooting solutions on the forum.  Anybody know where on the forum?  Obviously this thread has had numerous suggestions but mine still isn't working correctly.