Re: State Preservation and Restoration / Force Suspend

Subject: Re: State Preservation and Restoration / Force Suspend
From: Christopher Becom <email@hidden>
Date: Tue, 21 Apr 2015 12:15:08 -0400

From my bluetooth logs I have determined that the kill(getpid(), SIGABRT) command in fact kills the app and logs the event as a crash. The

[app performSelector:@selector(suspend)] first places the app in background and then suspended state.

To force the app to background, I dismiss the app from "App-Switcher"

On Mon, Apr 20, 2015 at 11:10 PM, Christopher Becom <email@hidden> wrote:

Hi

I am building an app that uses a peripheral manager object to advertise a service with a couple of read only characteristics.

It needs to continue to advertise in the background and then be ready to be put in background state from a suspended state as suggested in the CoreBluetooth Programming Guide via State Preservation and Restoration.

Right now I am trying to test if the app is successfully brought into a background state from a suspended state via the CBPeripheralManagerOptionRestoreIdentifierKey. A few of my tests have failed and I need to determine why.

First off, I am questioning if my app actually enters a suspended state when called. To test, I built a button event that calls

kill(getpid(), SIGABRT)

I also have a similar button event to enter background state calling

UIApplication *app = [UIApplication sharedApplication];
[app performSelector:@selector(suspend)];

To send an app to background by calling suspend seems counter intuitive. However, I did not find a call that sent the app to background.

Thank you very much for any advice you can provide.

 _______________________________________________
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

References:
	>State Preservation and Restoration / Force Suspend (From: Christopher Becom <email@hidden>)

Prev by Date: State Preservation and Restoration / Force Suspend
Next by Date: RE:IOS device act as both central and peripheral
Previous by thread: State Preservation and Restoration / Force Suspend
Next by thread: RE:IOS device act as both central and peripheral
Index(es):
- Date
- Thread