Apple

On 6 Jan 2013, at 20:42, Jonathan Cohn <email@hidden> wrote:

Thanks Andras, well at least Apple is aware of the problem and are possibly working on it. Perhaps ios24 :-)

Jonathan Cohn
(908) 812-9663

On Sun, Jan 6, 2013 at 3:24 PM, Andras Kovi <email@hidden> wrote:

There has been a similar question recently. The official Apple response was

"We're aware of this issue and are trying to come up with a solution. Currently, there is no workaround." (Jason Conn)

Regads,
Andras

On 2013.01.06., at 21:17, Darren Jones <email@hidden> wrote:

Is this standard behaviour for background apps? (I haven't bothered with backgrounding before now).
I'd have thought that even if the app is killed, it should be registered to receive events which I why I think maybe the App Delegate needs to be used?

Darren

On 6 Jan 2013, at 20:16, Jonathan Cohn <email@hidden> wrote:

I see this same behavior with my app. I usually get run times of about 45 minutes before the app is killed. I'm wondering if there is something we can do to reduce the memory size of the backgrounded app in order to prevent it from being closed by the OS. Has anyone else had any experience with this?

Jonathan Cohn

On Sun, Jan 6, 2013 at 2:47 PM, Darren Jones <email@hidden> wrote:
alls in the App Delegate?

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)

This email sent to email@hidden

References:
	>CBCentralManager runs in background, but eventually dies (From: Darren Jones <email@hidden>)
	>Re: CBCentralManager runs in background, but eventually dies (From: Jonathan Cohn <email@hidden>)
	>Re: CBCentralManager runs in background, but eventually dies (From: Darren Jones <email@hidden>)
	>Re: CBCentralManager runs in background, but eventually dies (From: Andras Kovi <email@hidden>)
	>Re: CBCentralManager runs in background, but eventually dies (From: Jonathan Cohn <email@hidden>)