Android 13 and AI2 build nb190b Bluetooth Client Problems

Bugs and Other Issues
#1

My APP was working OK until I updated my phone to A13.
Now, Bluetooth activity in the APP requests a permission for Bluetooth-Connect.
My original APP had no Bluetooth permission related blocks and was working OK.

Runtime Error
Need android.permission.BLUETOOTH_CONNECT permission for AttributionSource { uid = 10382, packageName = edu.mit.appinventor.aicompanion3, attributionTag = null, token = android.os.BinderProxy@1cdc6c9, next = null }: AdapterService getBondedDevices
*Note:* You will not see another error reported for 5 seconds.

AI2 version info indicates support of Android12:

Built: October 19 2022 Version: nb190b
Use Companion: 2.65 or 2.65u
Target Android SDK: 31 (Android 12.0)

BLUETOOTH_CONNECT permission does not appear in the Screen1 permission request list.
The existing permissions for "Bluetooth" and "BluetoothAdmin" does not make any difference when I add them to my code.

I have reviewed the Bluetooth related postings, tried adding the Client as an additional component as described in some postings. Nothing sees to make a difference in eliminating the error.

Can you confirm if this is an Android version support issue or something else ?
Thanks

1 Like
#2

Are you saying, this workaround does not work for you?

Please show a screenshot of your relevant blocks, i.e. how are you asking for the required permissions? See also

Taifun

1 Like
#3

I am not using BLE, just the classic BT; so I did not think the first reference applied to my problem.

Anke's solution shown in the second reference makes use of a permission that does not show up in my "call Screen1 for permission" block; so I do not know how to make use of it. Here is what my call block displays:

image
image626×521 16.4 KB

However, I have just seen this post from Ewan:

ewpattonMIT

Oct '22

The BluetoothClient/BluetoothServer permission issue should be addressed on this temporary test server: http://nb190a-bugfixes.ai2-ewpatton-temp.appspot.com/

When I tried that server, the missing BLUETOOTH_CONNECT permission appeared and I could incorporate it into my code.

image
image683×633 18.7 KB

With that permission in code, an Android message appears on the phone and upon confirmation, the permission is granted; and the program Bluetooth features work OK.

I can generate an APK using the new server and wait till the changes appear in the live version.

#4

Hi TGuneysu,

I followed your post about the BT problem with Android 13. Has a solution been found?

Thanks,
Tal