Apple

I have seen people complaining about CB getting extremely slow and erroneous if there are many devices paired. (Your scheme works only if pairing is done AFAIK. The iOS address change will prevent you from connecting to devices repeatedly if not paired.) The numbers mentioned were from 10-15+ . At 30 the system was pracically dead. I hope you can succeed with this approach but I have my doubts.

Using the i devices for an autonomous CB peripheral role just doesn't seem to be a viable option yet.

I hope Apple has heard our voice and made several improvements based on our input. There is several fields for making things better. Nevertheless, this is still the best support available in the whole industry.

Andras

Lucky you, got a ticket in the the available 70 seconds. Tell us if you are enlightened about the right way to solve your issue. :)

2013/5/23 Philip Brechler <email@hidden>

Am 23.05.2013 um 12:55 schrieb András Kövi <email@hidden>:

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 ;)

References:
	>Identify a iOS 6 "made" peripheral uniquely and persistently (From: Philip Brechler <email@hidden>)
	>Re: Identify a iOS 6 "made" peripheral uniquely and persistently (From: András Kövi <email@hidden>)