How would making the API block-based change the UUID-rotation business or the lack of "stopped advertisement" callbacks ?! Setting the allowDuplicates key to true when starting the scan, combined with a timeout, is also what I do. Note that in background mode, this won't work as "allowDuplicates" is forced to @NO there.
Etan > On 17.07.2013, at 02:04, "Rick Mann" <email@hidden> wrote: > > >> On Jul 16, 2013, at 17:00 , William Henderson <email@hidden> wrote: >> >> You can keep the CBPeripheral's you've seen around in some form and then compare UDID's to see if you need to query the device further. That said, the rotating UDID's business adds some complexity here. To get around this in my app, I connect to every peripheral I see and ask for what amounts to a static app-specific UDID. I use this to know whether it's truly a new device or just an existing one that's changed CBUDID's. > > Bah. That's expensive and complicated. This API would be a lot easier to use if it was block-based. > >> >> -- >> William Henderson >> Sent from my iPhone >> >>> On Tuesday, July 16, 2013 at 4:53 PM, Rick Mann wrote: >>> >>> >>>> On Jul 16, 2013, at 16:48 , William Henderson <email@hidden> wrote: >>>> >>>> I don't think so. What I do to work around this is allow duplicates and then have a timeout. If we haven't seen a peripheral for a few seconds, it disappears from the list. >>> >>> How do you de-dupe? >>> >>>> >>>> -- >>>> William Henderson >>>> Sent from my iPhone >>>> >>>>> On Tuesday, July 16, 2013 at 4:41 PM, Rick Mann wrote: >>>>> >>>>> Is it possible to tell when a peripheral has stopped advertising? When I'm showing my BLE connection UI, I list all the peripherals that come back. But when one of them went down (we cut power to the radio), it stayed in the list, because there's no notification I know of for when it goes away. >>>>> >>>>> Am I overlooking something? Thanks, >>>>> >>>>> -- >>>>> Rick >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >>> >>> -- >>> Rick > > > -- > Rick > > > > > _______________________________________________ > 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