CB is very unreliable
CB is very unreliable
- Subject: CB is very unreliable
- From: Rick Mann <email@hidden>
- Date: Tue, 23 Jul 2013 17:31:26 -0700
I've had to re-do some of the UI around our BLE interaction. Mostly, the code I'm using to call CoreBluetooth is the same, just when I call it has changed.
But I'm seeing a lot of unreliable behavior. For example, I started scanning, then after that, this happened:
2013-07-23 17:26:36.761 [9458:907] CoreBluetooth[WARNING] <CBConcreteCentralManager: 0x1f07e340> is not powered on
2013-07-23 17:26:36.896 [9458:907] <CameraBrowser.m:113>: centralManagerDidUpdateState: 5
2013-07-23 17:26:37.535 [9458:3c07] CoreBluetooth[ERROR] XPC connection interrupted, resetting
2013-07-23 17:26:37.537 [9458:907] <CameraBrowser.m:113>: centralManagerDidUpdateState: 1
2013-07-23 17:26:37.654 [9458:907] <CameraBrowser.m:113>: centralManagerDidUpdateState: 4
2013-07-23 17:26:45.389 [9458:907] <CameraBrowser.m:113>: centralManagerDidUpdateState: 5
It seems like I have to keep all sorts of parallel state (in this case, I have to keep the state that I want to be scanning, so that if CB powers up, I can actually start scanning again).
This is getting extremely frustrating.
--
Rick
_______________________________________________
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