Unfortunately that flag is ignored in background. This behavior has not changed in iOS6. I haven't seen any "regular" way to implement what you would like. However, there is a theoretical solution. I have not tried it yet but I suppose it should work. When you receive the didDiscoverCallback, the app gets about 10 seconds to run. During this, you may restart the scanning by stopping it first and then starting again. The question is whether restarting the scan clears out the cache while the app is backgrounded. Cheers, Andras On 2012.11.06., at 0:40, Rick Mann <rmann@latencyzero.com> wrote:

On Nov 5, 2012, at 14:40 , Nick Moen <NickM@npe-inc.com> wrote:

...

Has there been any update with iOS 6.0 that allows for the reset of CentralManager so that that same device can be discovered multiple times in the background? I have a device that I would like to trigger multiple callbacks to didDiscoverPeripheral in the background. I know there was no way to do this in iOS5 but I wanted to see if there were any updates.

There's the CBCentralManagerScanOptionAllowDuplicatesKey you can pass to -scanForPeripheralsWithServices:options:. Dunno what that does in the background, but if it's on in the foreground, you get advertising packets as long as you scan.

-- Rick

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/allprog%40gmail.com

This email sent to allprog@gmail.com

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.... This email sent to site_archiver@lists.apple.com