RE: Null UUID Returned for CBPeripheral
RE: Null UUID Returned for CBPeripheral
- Subject: RE: Null UUID Returned for CBPeripheral
- From: Michael Mallinson <email@hidden>
- Date: Tue, 25 Sep 2012 12:11:29 +0000
- Thread-topic: Null UUID Returned for CBPeripheral
Hi,
I’ve also seen this issue and reported it as a bug during the iOS6 beta. What I was seeing was that the UUID wasn’t filled in until after you’ve connected
to the peripheral. Once I had connected to the device, I have never had trouble with the UUID being null. To work around this I had to change my code to not store the peripheral until after you’ve connected to the device for the first time. Note that even
though the peripheral doesn’t have a UUID after scanning it, you can still connect to it. Also note that I didn’t see this behaviour on iOS 5.
Cheers,
--Mike
From: bluetooth-dev-bounces+michael.mallinson=email@hidden [mailto:bluetooth-dev-bounces+michael.mallinson=email@hidden]
On Behalf Of R. Justin
Sent: Tuesday, September 25, 2012 1:45 AM
To: email@hidden
Subject: Null UUID Returned for CBPeripheral
We're trying to access the UUID on the CBPeripheral object returned by the didDiscoverPeripheral.
The call peripheral.UUID will sometimes return a null value for a peripheral. We have verified that the uuid will sometimes be able to be pulled from the same device after the iPhone has been restarted or the Bluetooth has been reset.
We are wondering:
1) Is this a known issue?
2) Who else has seen this issue on the list?
3) Are there any workarounds?
4) Has a bug report has been filed for this issue? We are filing one now just in case.
Thank you and we appreciate everyone's advice and help in the matter.
|
_______________________________________________
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