FWIW, If you do not BLE pair, CBPeripheral.identifier is a cached value. You should use [CBCentralManager retrievePeripheralsWithIdentifiers:] to ensure that CBPeripheral instance is valid. Charles

On Jun 9, 2015, at 4:06 PM, Ben Levitt <ben@boostedboards.com> wrote:

We've encountered a pretty nasty bug in our iOS app, that seems to be somewhere in the bluetooth stack. Our app acts as a central, and connects to a ble module in a consumer device which acts as a peripheral. Our devices each have a BlueRadios nBlue module in them, that we connect to using the BlueRadios brsp iOS SDK. Everything works great most of the time, for most users. But for about 1 in 50 users, we see the following behavior:

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.... This email sent to site_archiver@lists.apple.com