Re: Unknown error 1309 in didFailToConnectToPeripheral
Re: Unknown error 1309 in didFailToConnectToPeripheral
- Subject: Re: Unknown error 1309 in didFailToConnectToPeripheral
- From: Moe Aboulkheir <email@hidden>
- Date: Tue, 04 Mar 2014 22:06:16 +0000
After some further investigation, I understand this a bit better. It turns out that it's only reproducible when connecting in an application which operates in both central and peripheral modes.
I got in touch with Apple via a TSI - I was told that several developers have complained about this, and that it is caused by a deadlock which happens when operating in both modes - the support worker suggested limiting to one mode at a time. When I followed up with the information that the error happened even when being extremely hygienic about mode switching (i.e. stopping advertising before scan, and vice/versa, even with long pauses between), he seemed to get a little confused.
I'm having a hard time convincing people that this bug is inevitable with any kind of interleaving of central & peripheral responsibilities in a single app. If anyone else has seen this, or if anybody can point to a successful CB application which uses both modes, and performs connections, that would be greatly appreciated.
Take care,
Moe
_______________________________________________
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