Multiple callbacks to didConnectPeripheral for the same peripheral device
Multiple callbacks to didConnectPeripheral for the same peripheral device
- Subject: Multiple callbacks to didConnectPeripheral for the same peripheral device
- From: Don Clark <email@hidden>
- Date: Mon, 16 Mar 2015 10:50:14 -0400
- Acceptlanguage: en-US
- Thread-topic: Multiple callbacks to didConnectPeripheral for the same peripheral device
I call connectPeripheral and set a timer. When the didConnectPeripheral delegate callback is made, the first thing it does is invalidate the timer. If instead the timer fires, the app will re-attempt the connection up to three times. I expected that the subsequent connectPeripheral calls to CB to connect to a given peripheral would override the previous request, and that's how it used to appear to work. Recently I've noticed that sometimes, after re-issuing the connect request, I'll get a second didConnectPeripheral callback for the same peripheral. This leaves me with the task of filtering out and ignoring the extraneous callbacks. Or not knowing whether I now have two connections open and must formally disconnect all but one?
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden