Re: Identify a iOS 6 "made" peripheral uniquely and persistently
Re: Identify a iOS 6 "made" peripheral uniquely and persistently
- Subject: Re: Identify a iOS 6 "made" peripheral uniquely and persistently
- From: Philip Brechler <email@hidden>
- Date: Thu, 23 May 2013 14:12:33 +0200
Sorry for miss sending my mails.Aside from this, I think using special randomly generated 128 bit UUIDs as service identifiers may be the answer for your case. You need to create a UUID when the app is initially set up and add a service with that ID to the provided services list.
Clients of your app would scan for the UUID of the service that your app provides. When they receive the didDiscoverPeripheral callback, they may find the special UUID in the advertisement data.
Right now I also think that this could be the only solution. Problem is that I don't get Service UUID at all in some situations. The whole Core Bluetooth Framework seems to be a little wobbly in this. One way could be to scan once, remember all found peripherals and then connect to these once. Every time your peripheral gets in close distance it would become "active".
Thanks for your thoughts!
Philip
PS: I guess I'll have a lab session at WWDC about this ;) |
_______________________________________________
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