Re: iPhone can no longer discover one specific peripheral
Re: iPhone can no longer discover one specific peripheral
- Subject: Re: iPhone can no longer discover one specific peripheral
- From: "Charles Y. Choi" <email@hidden>
- Date: Tue, 11 Aug 2015 14:33:14 -0700
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 <email@hidden> 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 (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden