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: András Kövi <email@hidden>
- Date: Thu, 23 May 2013 12:55:40 +0200
Hi Philip,
I suppose you know the fact that "local name" is not used when the app is in background and provided services are moved to the overflow area. Theoretically iOS devices handle the latter function but I have never been able to see the services from the overflow area on my Mac. Someone with two iPhones may provide evidence that it works. It hasn't happened on this list yet.
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.
This scheme should surely work if the peripheral is in the foreground and depends on whether the "overflow" case is handled by the i* devices correctly.
Let me know what you think. I haven't been able to verify my statements but based on my knowledge so far this seems to be a possible solution.
Regards,
Andras
_______________________________________________
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