Re: UUID is nil for newly discovered CBPeripheral
Re: UUID is nil for newly discovered CBPeripheral
- Subject: Re: UUID is nil for newly discovered CBPeripheral
- From: Glenn Maynard <email@hidden>
- Date: Thu, 23 Aug 2012 18:12:41 -0500
On Thu, Aug 23, 2012 at 11:04 AM, Joakim Linde
<email@hidden> wrote:
Please note that the lack of UUID does not prevent you from doing what I think you want to do (if that's not the case, then please explain to me what you are trying to do). In your app you can still check if it is the same CBPeripheral object that is being reported over and over again. Since the peripheral should use a random resolvable address that changes at least ever 15 minutes, the address will change and the device will appear to be a "new" device. The only way to long term be able to track device is to connect and pair with it. That way we will get the IRK to resolve the address and present that to you as a UUID.
Is this documented anywhere? I currently have a pairing UI that stores the UUID received from didDiscoverPeripheral when the user says to pair to a device, then we connect to that UUID from then on (through retrievePeripherals). This has worked consistently in my testing, but from the above it sounds like this may not always work, and it's troubling that the first I've heard of this is a random mailing list post (and it sounds like it's not just me).
--
Glenn Maynard
_______________________________________________
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