registration failed because app is scanning too frequently not being thrown by lib?

[mobilekosmos]

2026-08-20 08:54:49.706 16246-16353 BleScanRepo$runScan     com.myapp.myapp      D  runScan
2026-08-20 08:54:49.709 16246-16284 BluetoothAdapter        com.myapp.myapp      D  isLeEnabled(): ON
2026-08-20 08:54:49.710 16246-16284 BluetoothLeScanner      com.myapp.myapp      D  Start Scan with callback
2026-08-20 08:54:49.712 16246-16258 BluetoothLeScanner      com.myapp.myapp      D  onScannerRegistered() - status=6 scannerId=-1 mScannerId=0
2026-08-20 08:54:49.712 16246-16284 BluetoothLeScanner      com.myapp.myapp      E  registration failed because app is scanning too frequently

Shouldn't the lib throw an exception when the OS throws that "registration failed because app is scanning too frequently"?

[philips77]

I don't know if we get this callback.
Had the onScanFailed been called, it woud have forwarded the exception. Seems this is silently ignored my the os, while the library thinks the scan started.

We may do some heuristics by reporting an issue in no reports are reported, but this has a high possibility of false positive.

[mobilekosmos]

I already had a logic as a workaround "if no result in 5s restart scanning" but this leaves the user waiting despite the OS already knows what the issue is, could you request Google to offer something here? Because it was the same with their Jetpack Ble lib, it's weird that the OS does not throw anything.
To reproduce this it is very easy, just start a scan 6+ times in a loop under 30s