Re: How should CBPeripheralManager state changes be handled?
Re: How should CBPeripheralManager state changes be handled?
- Subject: Re: How should CBPeripheralManager state changes be handled?
- From: mihai sardarescu <email@hidden>
- Date: Mon, 23 May 2016 16:01:22 +0000 (UTC)
Hi Craig,
Do you have any recommendation on how to recover from a BT crash for example? Should I only rely on the user manually opening my application? Are there any other solutions to bootstrapping again the BLE configuration needed by my application without asking the user to manually open my application?
I am asking this as we have noticed during our testes that 1) iOS tends to restart frequently during the night and 2) the BT daemon seems to be crashing for our users every other day. So our users frequently complain that the remote device fails to connect to the iPhone over BT (basically my application enters a "limbo" state it can only recover from when the user opens it manually).
Thank you,
Mihai
On Wednesday, March 2, 2016 9:49 PM, Craig Dooley <email@hidden> wrote:
State restoration across reboot or BT crashes is not supported today.
- Craig
> On Mar 1, 2016, at 6:52 AM, mihai sardarescu <
email@hidden> wrote:
>
> Thanks, Craig. This is pretty much what we have done and it seems a lot more reliable.
>
> I would have one more question about the CBPeripheralManager state. Take the following example:
> * My application added the Bluetooth service and is advertising.
> * My application is sent to the background and then suspended or killed by iOS.
> * The Bluetooth chip resets.
> Will iOS handle this on its own (add the Bluetooth services of my application and start advertising)? Or will it wake up my application and my application has to add the Bluetooth services?
>
> Thank you,
> - Mihai
>
_______________________________________________
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