Minimum SDK... Play Store doesn't like my .aab

[Anke]

Use a valid app signing key to continue

Completely unnecessary, complicated, time-consuming, ... It only takes a few seconds to successfully upload a new app (as AAB) to the Play Store. As I have already explained several times in various posts and guides, you only need a new keystore (if the old one has already been used for other Play Store apps). Export and backup the current keystore. Delete the current keystore in the Designer (AI2). Reload the browser (not quite sure if necessary). Build the AAB (a new keystore is generated t…

[YoussefM]

Your solution worked.
Thank You.

[Corto21]

Which solution are you referring to specifically? I'm a bit lost on what the working solution is to solve the low SDK issue

[Taifun]

@Corto21

I'm a bit lost on what the working solution is

Both solutions work, the accepted one

Minimum SDK... Play Store doesn't like my .aab

This is a new feature of Google Play and has nothing to do with extensions. Specifically, Google now by default has a feature called "Automatic Protection" for apps, which if turned on injects new code into the AAB before it is converted into APKs to be distributed to users. The code Google injects requires the app be min SDK 21. It looks like if you turn it off you can upload AABs created by App Inventor without issue (like every app ever made up until Google introduced this new mechanism). Her…

As well as using the extension to set the min sdk to 21

Minimum SDK... Play Store doesn't like my .aab

minSdk21.aix (4.0 KB) Import and drag it onto the screen.

Taifun

[Corto21]

I used the first of the two proposals and it worked.
Thank you