peripheralManagerIsReadyToUpdateSubscribers not called after failed update

Question

Whenever I Disconnect and try to connect. I am not receiving peripheralManagerIsReadyToUpdateSubscribers and first update only fails.

I am following the below steps

Start Advertisement and establish connection with central.
Now try to update value in queue. First one will be success and second update will fail. Then I will receive peripheralManagerIsReadyToUpdateSubscribers, Then i'll continue update again.
Close connection with central, Remove services and start advertisement again and add services. Then i'll receive peripheralManager : didSubscribeToCharacteristic again and now If I try to update (updateValue:forCharacteristic:onSubscribedCentrals) always it fails and i'll never receive peripheralManagerIsReadyToUpdateSubscribers.

This behaviour is only with new iOS version 10.0.2. I am not facing this issue with older version of iOS like 9.3.3.

My app works great in iOS 9 but in iOS 10 I have the same issue. — KotaBear233, Oct 25 '16 at 16:23
No still waiting for response. If I am able to resolve i'll update. — user2017285, Oct 26 '16 at 04:57
Believe this is an iOS 10 issue. I wrote a bug to Apple about this. If you find anything else out please let me know. — KotaBear233, Oct 26 '16 at 14:25
A work around for this is to count the failures. And if its over 3-4 restart the service. I've only tested once so far, but this fixed it for me when I got into this weird state. — KotaBear233, Nov 01 '16 at 17:08
No. I am not able to resolve this. Without the help from apple or someone, I do not think will be able to resolve this issue. — user2017285, Nov 07 '16 at 05:01
I just got a workaround. Not sure that is a proper solution. If I re initialise CBPeripheralManager session then I was able to update value again. — user2017285, Nov 09 '16 at 11:33
Whenever I am doing stop advertisement, I'll do re initialise then again start advertisement. — user2017285, Nov 24 '16 at 09:02
I still have this issue in ios11. Can someone clarify, when you say reinitialise do you mean create a new instance of CBPeripheralManager? I'm doing that and it works. It feels a bit brute but... — Andrew, Feb 20 '18 at 16:43
@andy good that work around is working for you. So many people are facing the same issue but still no upvote for this question or proper solution for this question. — user2017285, Feb 22 '18 at 05:09
I'm still seeing the same issue in iOS 13...in 2020. Surprising that this is still the only answer and that Apple hasn't fixed it yet. I'll go search, but is there a particular bug report that I should be upvoting for Apple to see? — wildcat12, May 13 '20 at 14:57

peripheralManagerIsReadyToUpdateSubscribers not called after failed update

0 Answers0