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

MIT App Inventor Help
1

Trying to upload MIT App Inventor App to Play Store...

I get "Play installer check requires a minimum SDK version of 21 or higher. The uploaded App Bundle has a minimum SDK version of 7. Update the minSdkVersion in your app's Android manifest.
Couldn't upload. Try again."

Never had this problem before...

MIT App Inventor

Thank You!

P.S. Third attempt got this...

"Play installer check requires a minimum SDK version of 21 or higher. The uploaded App Bundle has a minimum SDK version of 19. Update the minSdkVersion in your app's Android manifest.

2

i think an extension which is not updated causing problem

3

I have the same problem :frowning:

1 Like
4

Are you using the latest nb199a and Companion 2.73a to build?

The key change in nb198 and this release is upgrading the Android SDK target to 34, which aligns with Android version 14. This update is essential as it will be mandatory for adding or updating apps on the Google Play Store after August 31, 2024.

1 Like
5

How do I change which version I'm using?
How do I know which version I'm using?
I thought this was handled... I updated a prior app and it cleared the Min SDK warning at play store.

6

The companion app also asserts a minSDK of 7 and MIT has never gotten an error from the Play Store about the minimum version

Can you provide screenshots of that message?

Taifun

7

The question is, which extensions are you using?
Probably it is an extension issue, which does not set the min sdk correctly?
You only can adjust the min sdk if you use a corresponding extension

For example this extension will set min sdk to 30

Taifun

1 Like
8

Tried it... same result.

9

What have you tried?

I don't see the answer to this question:

Publish your aia project here.

10

image
image1920×1080 227 KB

ps1
ps11920×1080 286 KB

11

I think you should ask the author of the admob extension if he has set the minSdk properly in his extension.

12

I tried the extension suggested for changing the manifest to min 30. No luck.

13

I don't see this extension in the screenshots. If you want, compile two versions of the APK, one without the extension setting minSdk to 30 and the other with this extension. Put this apk on your google drive and share the links here or in a PM. I'll check what minSdk both versions of the apk have.

In any case, from the message in Google Play you can read that your apk has minSdk set to 19, and it should have 21. I suggest contacting the author of the extension, because I do not know the mechanism of setting minSdk from several extensions. Perhaps despite using an extension that sets minSdk to 30, the admob extension still overwrites minSdk to 19.

14

I have the same problem please any solution ?

15

Admob too?

16

I think you didn't understand the question well
now google play console requires a minimum version of SDK 21 or higher (version of the app and not for the extension).
and you can check for yourself.

17

So please is there a method to set a minimum sdk version (for the app and not for extension)?
or we have to wait for the appinventor to resolve this problem?.

18

This is not true. Companion has minSdk set to 7 and is published without any problems. The problem is that the admob extension according to the play store requires minSdk21 and is set to 19. So it is only a problem of the admob extension.

19

AppInventor will not solve this problem because it is an extension problem and not app inventor. Test and publish the app without the extension in the Google Play console.

The minimum Android API level is 21

Starting in version 23.0.0, the Google Mobile Ads SDK requires all apps to be on a minimum Android API level 21 to run. To adjust the API level, change the value of minSdk in your app-level build.gradle file to 21 or higher.

For further questions, please contact the extension author.

20

did you drag the extension into the working area?
Taifun