CBCentralManager runs in background, but eventually dies
CBCentralManager runs in background, but eventually dies
- Subject: CBCentralManager runs in background, but eventually dies
- From: Darren Jones <email@hidden>
- Date: Sun, 06 Jan 2013 19:47:50 +0000
I successfully have CBCentralManager running in the background scanning for peripherals. I have theCBCentralManagerDelegate in a singleton method and have App communicates using CoreBluetooth in the .plist and like I say, it works great for hours in the background. The problem I have, is when my app is eventually completely killed because other apps have been used and need the memory space and my app is flushed, then my app is no longer woken by any of theCBCentralManager delegate calls and my peripheral will no longer connect. Is there something else I need to do to make sure my app is woken back up? Do I maybe need to have the CBCentralManager calls in the App Delegate? Should I be doing something in the App Delegate when the app is backgrounded? Thanks |
_______________________________________________
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