Beta version of BLE extension for Android 12 permission changes

[Anke]

Well, since I have to edit the manifest anyway, I might as well remove ACCESS_FINE_LOCATION there. At the moment, however, I also have the problem with my current work notebook that the "neverForLocation" flag is unknown in my APK Editor Studio version. It was probably added later by Google.

Unfortunately, the current APK Studio version cannot be installed on my ancient Win7 notebook. I'll have to try it on another Win10 PC or on my MacMini, later ..

[ChrisWard]

Hi Evan - is anything being sorted out for the Bluetooth Classic issue?

Re: Need Help In Bluetooth Permission for an app on Android 12 - #97 by Madhav

That is about a Bluetooth Classic permission error but has got overwhelmed with the BLE issue. See post#97 from Madhav, the original Topic author.

[ewpatton]

Correct. The flags feature was something added for SDK 31 and needs a newer version of the build tools even for us to compile with it, so I expect many other tools will need to be updated to take it into account.

[Madhav]

Hi Evan and Chris, I have figured out a way to solve this Bluetooth Classic Permission Issue.

1. Build the APK file from your project in MIT APP inventor.
2. Open the AndroidManifest.xml file to modify the permissions.
3. Delete all permissions related to BLUETOOTH and add 3 lines.

4. Save the AndroidManifest.xml file with above changes.
5. Rebuild the APK file.

NOTE:

1. How to view the AndroidManifest.xml?
   ------ Download APK Studio Editor from the link Download APK Editor for PC and Mac – APK Editor Studio
   ------ Open APK Studio Editor and Open the APK file.
   ------ Click on the "Open Contents" tab
   ------ Folder will be opened and "AndroidManifest.xml" file can be seen.

2. How to Edit AndroidManifest.xml file?
   ------ Open the AndroidManifest.xml using any of the text editor.
   ------ Delete the lines related to Bluetooth related permissions.
   ------ Paste the below lines and save the changes.

3. How to Rebuild the APK
   ------ After following the Step1 and Step2, On APK Studio Editor, Click on "SAVE APK"

Now, install the APK on mobile and Check the Bluetooth Permission Error Should be gone

[Anke]

@ewpatton

needs a newer version of the build tools even for us to compile with it, so I expect many other tools will need to be updated to take it into account.

Even with the latest version of apktool it is not possible to set compileSdkVersion=31:

[FEAT] - CLI Flag to optionally ignore SDK changes when recompiling.

compileSdkVersion value changed in AndroidManifest.xml file

It seems to be related to aapt2.exe (aapt.exe) - I'm not sure...
Please any tip/hint that might help?

[Anke]

@Madhav

1. Delete all permissions related to BLUETOOTH and add 3 lines.

If you set the targetSdkVersion=29 the app (APK) will not allowed by Google (in the Play Store). The minimum targetSdkVersion has to be 31.

[Anke]

@Anke

the app (APK) will not allowed by Google (in the Play Store)

BTW... (see here):

[Zivo]

Hi Evan,
Part of this release, what's the chance to fix the AdvertismentData block?
This module return null, seems it was never works.
I need it for some IOT class.

THX
Ziv

[ChrisWard]

Hi Evan, hope your brain is suitably refreshed after your short break

Re my Post#20 in this topic:

BLE extension - Date Built: 2023-02-23 - permissions & connecting issuses on Android 12+

Okay, so the solution should be the following: All devices, I want to use, contains "BTG" in the name. So I scan for a specific short period of time, then stop the scan and add all devices that contains "BTG" in the name to a list. Then repeat the process to find more devices with the correct name and add them to my list – if not there yet. Right?

To prevent the BLE Device List becoming so large it slows the Smartphone down or crashes the App, we need a new function that filters devices found and only adds them to the BLE Device List if a specific string exists.

[Mok_Ryun]

@ewpatton

your app doesn't get the BLUETOOTH_ADVERTISE permission if the app never uses the StartAdvertising block.

i could use scan with @Anke 's way that set "scan block" dummy for get connect permission in running!

but still "advertising" is not working.

it showing always "false" in result.
can i make it working with any ways??

[Anke]

@Mok_Ryun

can i make it working with any ways?

You are using Kodular. (You should ask there.)
Did you try it on AI2 too?

[Mok_Ryun]

yes and tested with after get "connect" permission.
still giving "false"

i didn't use APK studio. must i?

[ewpatton]

@Zivo

Part of this release, what's the chance to fix the AdvertismentData block?

I've been out for the past week, but I'll try to see if I can get this onto my calendar for this week.

[Mok_Ryun]

then, is it mean no way to use "advertisement" for now? (without APK studio?)

thank you for your support

[Mok_Ryun]

@Anke

You are using Kodular. (You should ask there.)

sorry but i tried with AI2 first, and i hoped its work with kodular and tried. so screenshot was.
whatever both are not working.

[Taifun]

to start scanning and immediately trying to connect to a device does not make much sense, does it?

try to use the DeviceFound event to connect

Taifun

[Mok_Ryun]

@Taifun

it was just for dummy for get permission when first run.

@Anke

So the BluetoothClient component has to be added again (as a dummy) to get this permission in the Manifest.

sometimes its asking permission when the just openned first time(without any actions), but sometimes its not asking. so i made button to activate. i don't know actual condition of these differences but i guess its from minimum SDK level or just AI2<->kodular build conditions.

ofc im using as you shown for event to find devices.

the problem and my purpose is to make permission for "BLUETOOTH_ADVERTISE".

thank you

[ChrisWard]

... that should be the Classic BT BluetoothClient block, not the BLE block, as per Anke's post.

[Anke]

@Taifun

to start scanning and immediately trying to connect to a device does not make much sense

@Mok_Ryun

it was just for dummy for get permission when first run.

So the BluetoothClient component has to be added again (as a dummy) to get this permission in the Manifest.

@ChrisWard

that should be the Classic BT BluetoothClient block, not the BLE block, as per Anke's post

BLE extension - Date Built: 2023-02-23 - permissions & connecting issuses on Android 12+

Yes, I think so. However, you must add at least one .Connect block to the Blocks area to get the android.permission.BLUETOOTH_CONNECT permission declared in the Manifest. According to my tests, this permission is generally required, even if it's just about listing (scanning) BLE devices. (I've already pointed this out elsewhere and let @ewpatton know about it.) <uses-permission android:name="android.permission.INTERNET"/> <uses-permission android:maxSdkVersion="30" android:name="and…

[Anke]

@Mok_Ryun

it was just for dummy for get permission when first run

You should then place a .Connect block in a way (unobtrusive and separate from your blocks/procedures) that avoids a Connection error / ConnectionFailed.