WatchOS 27 throttles BLE discoveries

Hi!

We have an app that highly depends on CoreBluetooth including scanning for peripherals with an advertised serviceUUID. Our app sets the CBCentralManagerScanOptionAllowDuplicatesKey flag to true while scanning. Receiving continuous discovery events about nearby devices is key to measure the RSSI before connecting.

Updating some of our test devices to watchOS 27 we noticed that our app is broken. To analyze further we created a simple app to compare behavior between watchOS 26 and 27, and the difference is clear. On the 27 device it behaves like the flag is ignored and we only receive a couple of callbacks to centralManager(_:didDiscover:advertisementData:rssi:) then it stops. We could not find any documentation declaring this as a new restriction or something regarding that has changed.

Is this a bug, or is there a way to get the old behavior on the new OS?

The example app used for testing is available here: https://github.com/levente-gulyas-skidata/WatchBLEExperiments

(Change the serviceUUID for testing if needed)

Thank you, Levi

Have you filed a bug on this and, if so, what's the bug number?

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

Yes, I have submitted FB25209657 (BLE in app scanning is throttled on watchOS 27)

Thanks,
Levi

You are correct that behavior has shifted starting in watchOS 27 (and iOS 27).

In this release, the system introduces stricter power management rules for CoreBluetooth. While earlier releases were more permissive, watchOS 27 now actively throttles BLE scanning with CBCentralManagerScanOptionAllowDuplicatesKey: true whenever the watch enters a sleep state (such as when the wrist is lowered, the display dims, or the screen idles). Continuous, un-coalesced discovery callbacks have a major impact on battery life, so duplicate reporting is suspended once the application processor goes to sleep.

When the watch display is actively awake and your app is in the foreground, continuous discovery events should still arrive normally.

Suggestions for adapting to the new behavior:

  • Targeted scan windows: Trigger scanning only upon explicit user intent (like a wrist raise or button tap), sample RSSI over a short window (1–3 seconds), and then initiate the connection or stop the scan before the screen sleeps.
  • Coalesced background scanning: If you need to monitor for peripherals in the background or during sleep, rely on standard coalesced discovery (CBCentralManagerScanOptionAllowDuplicatesKey: false), which is designed to work within system power budgets.