iPhone SE BLE issue: delay in firing didConnect callback

Question

Created Dec ’20

Replies 3

Boosts 0

Participants 3

Hi members,
i 've an issue on iPhone SE 2nd gen (iOS 14.2) when my app uses CoreBluetooth API during the connection phase.

When my app call "connect" function to the peripheral,sometimes it happens that didConnect is fired after a delay of 45 or 90 seconds.
With iPhone 6 (iOS 12.4.9) and iPad 6th gen (iOS 14.2) this doesn't never happens.
Anyway, delayed or not, the didConnect is always fired successfully, so it seems it's only a matter of waiting for CB API to fire this callback.

I've just patch this strange behaviour with the following workaround: if didConnect callback is not fired within 3 seconds, the app cancel the current connection and retry to connect to the peripheral. To be sure I repeat this workaround for 3 times.

Does anyone faced this issue before?

Thanks

Answered by Javaz81 in 657992022

@erics-jca
Yes, it seems to have been fixed in iOS 14.3, but due to the fact that the event seems to occur randomly, I cannot personally be sure that the bug has been completely fixed.

Boost

Answer 1

erics-jca OP

Jan ’21

We are having BLE issues with iOS 14.2 as well (iPhone 11 and not iPad) and it seems very similar. Are you having the same issues with iOS 14.3? We're still investigating, but 14.3 seems better.

Thanks.

0

Answer 2

mromerC OP

Jan ’21

Hi There.

We faced the same problem and we implemented the same workaround.
I am not an electronic guy but from my point of view, it seems a hardware issue because it doesn't happen on other iOS devices using the same iOS version.

0

Answer 3

Javaz81 OP

Jan ’21

Accepted Answer

@erics-jca
Yes, it seems to have been fixed in iOS 14.3, but due to the fact that the event seems to occur randomly, I cannot personally be sure that the bug has been completely fixed.

0