[Bug]: Android 13: not able to get grant access for Bluetooth about flutter-permission-handler

[mvanbeusekom]

Hi @SteMMo33,

According to the log message it seems like you are missing a particular permission in your app/src/main/AndroidManifest.xml file. Based on the code snippet included in your issue description the missing permissions would be android.permission.BLUETOOTH_ADVERTISE.

Can you try adding this particular permission to your app/src/main/AndroidManifest.xml file and let us know if that helped?

[SteMMo33]

Hello,
just added the additional permission but the result is the same:

D/permissions_handler(28499): Bluetooth permission missing in manifest
I/mali_gralloc(28499): register: id=0x2fe00000ae1, importpid=-1
D/CompatibilityChangeReporter(28499): Compat change id reported: 78294732; UID 10233; state: DISABLED
I/flutter (28499): Statues: {Permission.location: PermissionStatus.granted, Permission.bluetooth: PermissionStatus.denied, Permission.bluetoothScan: PermissionStatus.granted, Permission.bluetoothAdvertise: PermissionStatus.granted, Permission.bluetoothConnect: PermissionStatus.granted}
I/flutter (28499): [scan] NoPermissionDlg

Thanks!

[Blue-Cheesecake]

Which version of Android API that you used? I got this similar problem on API 28, and 31 but work fine on API 33, and 34 (Don't know why). Try to test your app on different Android API.

@SteMMo33

[SteMMo33]

In the SDK Manager I set Android 14.0 - API 34 rev.2 - not 34-ext8 or 34-ext10.
Hope this help ..

[SteMMo33]

@Blue-Cheesecake
Now the context is:

• running on phone with Android 13 - API 33
• compileSdkVersion 33
• targetSdkVersion 33

In the 'Run' window I see:

D/permissions_handler( 3216): Bluetooth permission missing in manifest
I/flutter ( 3216): Statues: {Permission.location: PermissionStatus.granted, Permission.bluetooth: PermissionStatus.denied, Permission.bluetoothScan: PermissionStatus.granted, Permission.bluetoothAdvertise: PermissionStatus.granted, Permission.bluetoothConnect: PermissionStatus.granted}
I/flutter ( 3216): [scan] NoPermissionDlg

I'm wondering why it reports 'Bluetooth permission missing in the manifest' ..

[mvanbeusekom]

Hi @SteMMo33,

Sorry for the late reply (holiday got in the way). One thing I just thought of, during compile time the Android compiler will merge different AndroidManifests (including manifest specified in libraries) into one final manifest. On possibility would be that the bluetooth permission is removed during this merge proces. Luckily Android keeps a log file of the merge process which can be found in the build/app/outputs/logs folder.

Could you go through this log file to check if the bluetooth permissions are added? Alternatively feel free to share the log here so we can help analyse it (not sure if the file contains sensitive information though).

[ray007]

When I'm checking permission for bluetooth on android, it seems to be denied.
Trying to request it does not change it.

But I can ignore that and get permission for bluetoothScan, which works as expected...

[malgorzatakus]

Bluetooth permission is a legacy permission for older devices as you have in manifest android:maxSdkVersion="30"

So you are requesting a permission that you are not able to get granted since it is not there any more for your sdk. See here about bluetooth permissions: https://developer.android.com/develop/connectivity/bluetooth/bt-permissions

Is that make sense?

[ray007]

Would be nice if such legacy permissions were recognized as such and considered automatically granted.

[SteMMo33]

Thanks a lot for the link.
I think it is a little complex but I'll study the official documentation.
Thanks again.

[mvanbeusekom]

Would be nice if such legacy permissions were recognized as such and considered automatically granted.

Problem is that the Bluetooth permission has been replaced with more fine grained permissions starting from Android API 30. In other words on API 29 and below the permission is still valid, while on API 30 you'd have to use BLUETOOTH_SCAN, BLUETOOTH_CONNECT and BLUETOOTH_ADVERTISE instead. The old BLUETOOTH permission is no longer valid, returning an automatic granted would give a false positive.