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: Etan Kissling <email@hidden>
- Date: Thu, 23 Aug 2012 09:35:37 +0200
Hi Peter,
That's actually intended if you look into the header files. It says
that a UUID is
generated on the first connection. Of course, this leads to problems and does
not make sense, as a device can be uniquely identified by its BdAddr that is
already nown in the advertising stage. I imagine that the reason for
this is again
"privacy" related, as UUIDs for peripherals change from phone to phone.
An option would be to send the BdAddr in the advertising report.. With
this, you
could at least compare devices. However, you won't be able to create a custom
CBPeripheral instance from it by supplying it to retrievePeripherals.
I also filed a bug report for this, and it was closed as being a
duplicate. However,
the more bug reports there are for a single problem, the more importance it
receives and the higher is a fix prioritized.
Etan
On Thu, Aug 23, 2012 at 12:51 AM, Peter Skinner <email@hidden> wrote:
> Hello,
>
> I've encountered a surprising situation. In iOS6 b4, didDiscoverPeripheral
> delivers a CBPeripheral with UUID set to nil. This only happens the very
> first time CoreBluetooth encounters a new bluetooth hardware mac address.
> The next time it sees that address, it uses what seems to be a cached
> version of CBPeripheral.
>
> The UUID is set to a proper value sometime after discovery. We have several
> applications published right now that count rather heavily on UUID having a
> non-nil value in didDiscoverPeripheral.
>
> Is it time to start updating those applications and stop relying on the
> UUID, or should this be a bug report?
>
> If anyone has seen this, or knows what the expected behavior is, I'm all
> ears.
>
> Thanks!
>
> Peter Skinner
>
> Ten One Design
> 201-965-0200
> tenonedesign.com
> @psidentity
>
>
> _______________________________________________
> 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