Thanks for the responses. I’ve decided to try and make my app idea work with background peripheral and foreground scan, which I believe should work just fine, however i’m having mixed results.
I can have a peripheral broadcasting fine in the background and after 2 days of not using the device, I can still detect and connect to it :)
On my iPad mini, I detect it broadcasting in the background, but when I load up a memory intensive game (and I assume kills my app) then the peripheral is no longer detectable until my app is relaunched.
Is CoreBluetooth not meant to keep my peripheral broadcasting all the time?
Thanks
You could submit a TSI requesting the clarification you need. Be specific though. This is the quickest way to get access to the engineers. Otherwise, wait for WWDC labs :)
Cheers,
Chris
On 6 Nov 2013, at 2:49 am, András Kövi <
email@hidden> wrote:
But does best effort mean: include nothing at all times? Usually I have a single service advertised. Even that doesn't fit in? I feel like the implementation should adhere at least to what the documentation says it does. If it doesn't do anything, then why bother even mentioning it. :)
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