Could the problam also occur when your app runs in peripheral mode, while a completely separate app runs in central mode concurrently? On 04.03.2014, at 23:06, Moe Aboulkheir <moe.aboulkheir@gmail.com> wrote:
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 (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/kissling%40oberon.ch
This email sent to kissling@oberon.ch
_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.... This email sent to site_archiver@lists.apple.com