Target API level 31

MIT App Inventor Help
73

Yes, the latest version (4.3.2) targets SDK 31.
But you need to add

android:exported="true"

in the Manifest also for extensions (if necessary).

A simple way to check this is to build the APK and test it on an Android 12 device. If that works, everything is ok. Otherwise, you must edit the Manifest.

1 Like
74

What software did you used to create aab?
because the aab may be corrupted, try to recreate aab from apk or try to recreate the apk with apk easy tool

75

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

76

I´ll try that. Thank you.

77

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.

Screenshot (6)
Screenshot (6)1061×400 18.7 KB

78
79

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

80

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.

1 Like
81

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

82

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

83

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

84

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

85

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

Taifun

86

solution with video tutorial working for me

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
2 Likes
87

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

88

no funciona

89

may i know the error ?

90

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

Also I am one of your viewers
2 Likes
91
92

@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