• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: UUID
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: UUID

  • Subject: Re: UUID
  • From: Darren Jones <email@hidden>
  • Date: Sat, 09 Feb 2013 12:03:00 +0000
Sorry everybody. I must have been mistaken.
I have trialled by deleting app and also reinstalling iOS 6.1.1 and the UUID's did in fact stay the same for my peripherals.

I don't know what I did when I first posted this, I guess I must have cleared my NSUserDefualte where I store the UUID.

Darren

On 8 Feb 2013, at 17:00, Davis Walker <email@hidden> wrote:

If the OP is correct, this is a bug in my opinion, and should be reported to Apple.

The guidelines for "pairing" with a peripheral are to save that peripheral's UUID and retrieve the associated peripheral on app launch. If the UUID changes out from under the app then this can't be done. I'm sure there are ways to work around it, but I also think it's worth a bug report.

Dave


On Fri, Feb 8, 2013 at 6:09 AM, Etan Kissling <email@hidden> wrote:
Well,

for discovery:
take the BDADDR and put it into the manufacturing data:
- your app can see this manufacturing data and does not have to deal with the iOS "privacy" "feature".

for retrieveConnectedPeripherals:
take the BDADDR and put it into a characteristic:
- manufacturing data is not available for peripherals that are already connected to another app.

for retrievePeripherals:
as BLE connections can only be established after an advertisement packet is received, you can safely
ignore this method. Use scanning and the standard discovery procedures to reconnect to a peripheral
when you don't know the iOS UUID. Will have a similar latency than connecting to a CBPeripheral that
was obtained using retrievePeripherals.

or if you want a clean solution:
let the user re-pair the peripherals with your app. I'm not sure whether the UUID-cache is also wiped when
you perform an OTA upgrade of iOS, and from the user experience perspective, pairing should be a painless
mechanism anyways.

Etan


On 08.02.2013, at 14:58, Khaos Tian <email@hidden>
 wrote:

But it seems that CoreBluetooth doesn't allow you to access BDADDR. For some cases, people generate an UUID based on BDADDR and advertise it. I'm not sure this will work for Darren.

Best Wishes,
Khaos Tian

On Feb 8, 2013, at 9:55 PM, Etan Kissling <email@hidden> wrote:

Each of your peripherals already has a unique ID, its BDADDR. 

On 08.02.2013, at 14:53, Darren Jones <email@hidden>
 wrote:

This would have to be unique to each individually built peripheral.
I'm not sure that would be possible.



On 8 Feb 2013, at 13:51, Khaos Tian <email@hidden> wrote:

Maybe you can set an extra UUID characteristic in your peripherals or let it advertise an unique id in Manufacturer Data.

Best Wishes,
Khaos Tian

On Feb 8, 2013, at 9:20 PM, Darren Jones <email@hidden> wrote:

Thanks Andras,

What would be the best method to remember a peripheral?
In my case, I want to use a custom pairing method, so my app will only connect to peripherals that have been set up with that phone, and ignore others.

I have this working currently by remembering the UUID or each peripheral, however this is no good if they can change.

Thanks

On 8 Feb 2013, at 13:17, András Kövi <email@hidden> wrote:

Surely yes! If the BT stack is reset, new UUIDs are generated. You should use the UUID as an opaque value. It should not have any meanining to your application and your app should always check the response of the system with operations that are concerned with UUIDs.

Regards,
Andras


2013/2/8 Darren Jones <email@hidden>
After installing iOS 6.1.1 beta, I noticed that my app no longer recognised the UUID's of 2 bluetooth peripherals I have.

I think I read someone say that iOS creates the UUID for each peripheral based on it's MAC address and other things.

Could iOS give a peripheral a different UUID after updating iOS?

Thanks

Darren
 _______________________________________________
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


_______________________________________________
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


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: 
 >UUID (From: Darren Jones <email@hidden>)
 >Re: UUID (From: András Kövi <email@hidden>)
 >Re: UUID (From: Darren Jones <email@hidden>)
 >Re: UUID (From: Khaos Tian <email@hidden>)
 >Re: UUID (From: Darren Jones <email@hidden>)
 >Re: UUID (From: Etan Kissling <email@hidden>)
 >Re: UUID (From: Khaos Tian <email@hidden>)
 >Re: UUID (From: Etan Kissling <email@hidden>)
 >Re: UUID (From: Davis Walker <email@hidden>)

  • Prev by Date: Re: clearing Cached Peripheral Data/Seeing New UUID's
  • Next by Date: reading value for non-notifying characteristic
  • Previous by thread: Re: UUID
  • Next by thread: RE: A2DP with AAC codec: non-existent document reference in the "Bluetooth Accessory Design Guidelines for Apple Products"
  • Index(es):
    • Date
    • Thread