UUID is nil for newly discovered CBPeripheral
UUID is nil for newly discovered CBPeripheral
- Subject: UUID is nil for newly discovered CBPeripheral
- From: Peter Skinner <email@hidden>
- Date: Wed, 22 Aug 2012 18:51:40 -0400
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.
|
_______________________________________________
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