Re: CoreBluetooth cache clearing

Subject: Re: CoreBluetooth cache clearing
From: Steve Jabs <email@hidden>
Date: Tue, 22 Sep 2015 16:47:16 -0400

I've seen the same with kCBAdvDataManufacturerData. When viewing the raw bytes on each scan, and the peripheral changing said bytes, we'll see it with the old set of bytes on some rescans.

Steve Jablonski
p. (814) 720-9067
e. email@hidden

On Tue, Sep 22, 2015 at 4:12 PM, Héctor Cen <email@hidden> wrote:

UPDATE:

We performed a test with the LightBlue app and obtained interesting results:

On opening LightBlue, the app shows a list of the BLE devices nearby, in the case of our peripheral it shows the old name, but when i tap in the device and the app connects to it i can see the services and characteristic, nothing out of the ordinary, then the peripheral disconnects the connection from LightBlue (it is designed that way) and then when LightBlue scans again for devices nearby then it show the new name.

Is there some sort of special CoreBluetooth connection API that allows LightBlue to see the device’s real name? How to achieve this programatically?

Thanks again!

--
Héctor Cen
Sent with Airmail

On 22September, 2015 at 14:59:09, Héctor Cen (email@hidden) wrote:

Hi everyone!

This is a issue many developers face during the development of apps using CoreBluetooth. When connecting to BLE devices, CoreBluetooth caches the peripheral in order to reconnect faster later, i presume. But if for any reason, peripheral developers, we in this case, decide to change the peripheral name, then an iOS device that has previously connected to this peripheral would stop connecting to it because it would read it with its previous name. There’s no problems with iOS devices that hasn’t connected yet since they will connect to it with its real name.

I’m checking for the device name both in centralManager:didConnectPeripheral and in peripheral:didDiscoverCharacteristicsForService:error and the both show the previous name.

Is there a way to clear CoreBluetooth cache or force the rediscovery of everything about the peripheral so we we can get the right device name? Or is there an alternate way to check if it is the device iOS needs to connect to?

I’ve already tried turning off and on Bluetooth, WIFI, reset network settings.

The peripheral we’re working with is a Microchip RN4020 (I know, not the best one out there…)

Thanks in advance.

--
Héctor Cen

_______________________________________________
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

 _______________________________________________
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

References:
	>CoreBluetooth cache clearing (From: Héctor Cen <email@hidden>)
	>Re: CoreBluetooth cache clearing (From: Héctor Cen <email@hidden>)

Prev by Date: Re: Bonding completed notification
Next by Date: Re: Bonding completed notification
Previous by thread: Re: CoreBluetooth cache clearing
Next by thread: Bonding completed notification
Index(es):
- Date
- Thread