Target API level 31

[Genaro_Cardenas]

I used an app from Play Store called APK to AAB Converter

[Genaro_Cardenas]

I´ll try that. Thank you.

[Alex34]

Hello, big hug to all.

My first post here.

I did all the steps of the Thunder-thing post and went to the end.
more when publishing the .aab to my google account.

This is an error.

The Android App Bundle has not been signed.

[Anke]

@Alex34

The Android App Bundle has not been signed.

How many days to Launch Android api 31 to update

Export keystore from AI2 import it to the AI2 test server import your project (aia) with the same project name in the AI2 test server set the VersionCode to n+1 (build the APK and check if it is possible to be installed on Android 12; if not → report) build the AAB upload the AAB to the Play Developer console as an internal test track (internal testing) wait for the Pre-Launch report (1-2 hours) if there are no errors / warnings, download the APK from the Play Developer console test this APK o…

The app bundle you uploaded should normally be signed with the certificate associated with the thumbprint

Has the app already been published in the Play store? In other words, is it an update? If not: Change the current project name (from e.g. "myApp".aia to "my_app".aia). Make a backup of the keystore on the AI2 test server and store it in a safe place (on your PC and / or external SD card). (Note: If you haven't created any other apps here yet and published them to the Play Store, you can skip this step!) Delete the keystore and reload the browser. Create the AAB on the test server. Create a n…

[Miguel_Donoso]

alguna respuesta con respecto a poder cargar una nueva app con api 31???

[SteveJG]

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 compiler intended principally for educational purposes and experimentation.

MIT makes ever effort to make App Inventor available for all developers as soon as possible. Sometimes its self imposed goals and deadlines are delayed.

[Anke]

@Miguel_Donoso

upload a new app with api 31?

Try the test server (which already taegets SDK 31).

BIG PROBLEM ! WITH API30 in Google Console

IT WORKS !!!! THANK YOU ANKE !!! YOUR THE BEST !!! Here is the link to the test server app : http://ai2-test.appinventor.mit.edu.ezproxy.canberra.edu.au/

[weslei_souza]

Do I pay someone to solve this problem, someone willing?

[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.ezproxy.canberra.edu.au/
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.ezproxy.canberra.edu.au/
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.ezproxy.canberra.edu.au/
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.ezproxy.canberra.edu.au/
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).