Target API level 31

[Thunder-thing]

What problem are you trying to resolve??
If you want to change sdk target version, use this post.

[Genaro_Cardenas]

Hello, i've been absent since two weeks. I still can´t upload my .aab file. PLEASE HELPPPPP:(

[Taifun]

You found the correct thread which is great... however you forgot to read the contributions, especially this one

Target API level 31

MIT hoped to have the Android api 31 update by the end of August. It will be deployed and available whenever the software receives approval from Google and the release is ready. When the software is updated, you will find a notice here Release Notes for MIT App Inventor 2 . There are alternatives to waiting for the official release: Try Anke's advice Target API level 31 - #9 by Anke Code your commercial apps in Android Studio or Delphi Community Edition, or B4A instead of a great compil…

Taifun

[TheCodingBus]

solution with video tutorial working for me

How to change Target API level 30 to 31 in MIT App Inventor 2

How to change Target API level 30 to 31 in MIT App Inventor 2
Follow the steps-:

1. Open the Main site of the MIT App Inventor http://ai2.appinventor.mit.edu/
2. Open Your App.
3. Now Click on the Project and export the aia file of the selected project.
4. Now Open the Test version of the App Inventor link -: http://ai2-test.appinventor.mit.edu/
5. Now Click on project and import the aia file that you have recently exported.
6. Now go again the main site http://ai2.appinventor.mit.edu/
7. Click on the project and select Export Keystore
8. Now Import the keystore in your test version of the app inventor http://ai2-test.appinventor.mit.edu/
9. Now Build the aab file and upload this file to playstore

[Thunder-thing]

Yes you can retry building ur apk and/or creating test apk to see if its your app that have a problem.

[Liz_Mora_tinjacca]

no funciona

[TheCodingBus]

may i know the error ?

[AyProductions]

@TheCodingBus The best solution can be to wait for a few days, or use APK Editor studio Since API 31 update will be coming soon!

Also I am one of your viewers

[Anke]

@Liz_Mora_tinjacca

no funciona

@TheCodingBus

may i know the error

Android 12 changes

Anyone facing this problem after targetSdk 31 when using extensions has two options: Contact the extension developer(s) and ask them to declare this (android:exported="true" for activities, broadcast receivers) in the Manifest. Build the APK, decompile it, declare it in the Manifest, recompile the APK, convert the APK to AAB and sign it. See also here: New App API Level 31 In Console - #2 by Anke - Discuss - Niotron Community Example: [grafik] Note: Taifun has already fixed it in…

[Ploy_V]

@Ridoy1 Here I use VS code and APKLab extension

1. Open VS code just the program
2. CTRL + Shift + P ➜ APKLab: Open an APK
3. For edit Manifest AndroidManifest.xml replace android:exported="false" > android:exported="true"
4. For set targetSdkVersion change in apktool.yml then save
5. Right-Click on or inside apktool.yml file ➜ APKLab: Prepare for HTTPS inspection
6. Right-Click on or inside apktool.yml file ➜ APKLab: Rebuild the APK

now I have only memory heap error so this may work if my memory is enough

[Uniti_Anello]

Hi, I did it, the app was loaded correcly and availlable for alpha test but, at start, a message "The permission READ_EXTERNAL_STORAGE was denied" appears. No problem with the same app built with "standard" ai2 and installed using apk.
There is a known walkaround?
Thanks

[ChrisWard]

@Prof_Carlos_Franca

There are options to try to generate the AAB File on the KODULAR Platform.

App Inventor already has this option (which is probably why Kodular has it, as Kodular is basically a clone, using MIT's Open Source).

[Anke]

@Uniti_Anello

I did it, the app was loaded correcly and availlable for alpha test but, at start, a message "The permission READ_EXTERNAL_STORAGE was denied" appears. No problem with the same app built with "standard" ai2 and installed using apk.

That should not happen. In order to understand/investigate the problem, we need the aia.
So post the aia or send it to me via PM.

[Anke]

I took a look at your aia. Your app has 17 screens. It should usually be no more than 10.

I haven't tested your app. But maybe READ permission is no longer automatically requested on the test server (targetSdk 31).

So request this permission manually (e.g. in the Screen.Initialize event):

Build the APK, try and let us know ...

[Uniti_Anello]

Thanks.
I'll try

[Uniti_Anello]

Thanks. The permission works now, but I have another problem.
The signature key seems to be changed from last build i did with ai2-test and google play refuse a new release. The app is published as internaal test and seems non possible to delete and make a new one.
Whai I can do ?

[Anke]

@Uniti_Anello

The permission works now

Which component does no longer request READ permission (automatically)?

[Anke]

@Uniti_Anello

The signature key seems to be changed from last build i did with ai2-test and google play refuse a new release.

• Export the keystore from the AI2 server and
• import it on the test server.
• Set the versionCode to n+1,
• build the AAB and
• upload it to the Play Developer console as an internal test track.

[Uniti_Anello]

These are the blocks generating the error. I suppose in writing the downloaded image file to filesystem

[Anke]

What does this have to do with the keystore?
And post all relevant blocks ...

Take a Label, set fileName to it and post the "Do it" result.