Bluetooth and Nearby Devices Permissions: Split the Version Paths

Name the actual Bluetooth operation

Follow the Bluetooth permissions guide for API-specific declarations, including when legacy permissions should be limited to older versions.

Do not assert “never for location” casually

A neverForLocation assertion should reflect the actual use of scan results. It is not simply a switch to avoid explaining location access. The platform documentation notes behavioral consequences, including filtering in some scenarios.

If the feature derives physical location from Bluetooth information, model and disclose that use honestly rather than declaring otherwise to simplify the prompt.

Check grants at the operation boundary

Request the applicable nearby-device access when the user pairs or connects a device, not at unrelated app startup. Handle denial, Bluetooth being disabled, no devices found and the device disconnecting after a grant.

A granted permission does not mean the adapter is enabled or that the target peripheral is reachable.

Test a useful compatibility matrix

Test a supported older Android release, Android 12-era nearby permissions and current target/device behavior. Include a fresh install, denied scan access, granted connection access and revocation after pairing.

Use representative peripherals. A test against one device model cannot prove compatibility with every Bluetooth service or manufacturer implementation.

Inspect the release manifest

APKLint's permission checker can help identify scan, connect, advertise and legacy declarations. It cannot determine radio availability, peripheral behavior or whether the app uses results for location. Keep the manifest review alongside runtime pairing and reconnection tests, with an explanation for each requested capability.