A "strong assertion" does not help safely exclude android.permission.ACCESS_FINE_LOCATION from manifest

It is said that "Currently on Android the android.permission.ACCESS_FINE_LOCATION permission is requested together with Bluetooth permissions. This is required for Bluetooth to work properly, unless the application provides a strong assertion in the application manifest that it does not use Bluetooth to derive a physical location":
https://doc.qt.io/qt-6.7/qbluetoothpermission.html#requirements

But my reproducer cannot properly get Bluetooth permission granted unless I have android.permission.ACCESS_FINE_LOCATION in my manifest. A strong assertion of

android:usesPermissionFlags="neverForLocation"

does not help.

In detail, my manifest defines permissions like:

    <uses-permission android:name="android.permission.INTERNET" />
    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
    <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
    <uses-permission android:name="android.permission.BLUETOOTH_ADMIN" />
    <uses-permission android:name="android.permission.BLUETOOTH_SCAN" android:usesPermissionFlags="neverForLocation"/>
    <uses-permission android:name="android.permission.BLUETOOTH_ADVERTISE" />
    <uses-permission android:name="android.permission.BLUETOOTH_CONNECT" />

Deploy as it is and click button to request permission - it fails anyway even though you "allow". You need to add

<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />

to make it work.

Built with Android platform SDK 34 and tried both Android 14 and 15 devices.