Google Playstore Target API level requirements

I get the following error when I publish on Google Play Store. How do I resolve it? Thanks

"Target API level requirements from August 2020


Your app currently targets API level 28 and must target at least API level 29 to ensure it is built on the latest APIs optimized for security and performance."

Oh! This is actually something that we have to fix on our side. Thanks for reporting! If you’re still able to publish for now with this error, you can go ahead, but we will publish a new version of our runtime which includes the API level bump!

1 Like

This is actually already fixed with client runtime version 1.9.15 – can you try rebuilding with that client version?


Thanks for the responses… I rebuilt with 1.9.15 and that specific warning is now gone but I do get the following warnings (See screenshot). I’ll paste them here for anyone searching the same.


This APK results in unused code and resources being sent to users. Your app could be smaller if you used the Android App Bundle. By not optimizing your app for device configurations, your app is larger to download and install on users’ devices than it needs to be. Larger apps see lower install success rates and take up storage on users’ devices.


This APK contains Java/Kotlin code, which might be obfuscated. We recommend you upload a deobfuscation file to make your crashes and ANRs easier to analyze and debug.


This APK contains native code, and you’ve not uploaded debug symbols. We recommend you upload a symbol file to make your crashes and ANRs easier to analyze and debug.

These are just Google advertising their managed App Bundle which we can’t provide since it defers APK generation and signing to Google Play and also tips to improve debugging your app through Play Store portal, which we are not providing at the moment.

i.e. this will not majorly affect your app in any way.

Great… I was able to submit the app without a problem. Thanks

There is a notification in Google play that they will need apps targeting API level 30 in august. I get a general error when I try to use the newest build (2.8.31) but 2.6.8 works without any errors.

Yes, i have some issue too with this fact.
Are there any solutions for the API at level 30?

Android: The time has come again for the API Level upgrade. This time with API Level 33.

I got the following message while submitting the app. I compiled with the latest runtime:
Update your target API level by August 31, 2023 to release updates to your app
We’ve detected that your app is targeting an old version of Android. To provide users with a safe and secure experience, Google Play requires all apps to meet target API level requirements.

From August 31, 2023, if your target API level is not within 1 year of the latest Android release, you won’t be able to update your app.

To continue making updates to your app, ensure your app targets Android 13 (API level 33).

1 Like

It’s OK with : Runtime Version: 4.9.72

No, its not solved. I have published with this version and have the warning from google. The version referred to by this warning was built with 4.9.72

For my app, this successfully upgraded the SDK to version 33.

1 Like

Maybe I´m using some features that mean the build has to fall back to the older API. Either way, its a big issue.

Hi @Phil_Evans,

Could you please check the SDK version in the Google Play Console, as @J.Luc has posted? We have tested several submissions with 4.9.72 and could not reproduce the warning.

Hi @Kirill_Leventcov , Looking now I can see it says 33 like J. Luc?. The warning is still there from google though. I have no other live versions.

I will investigate more and report back

I´ve followed the error … playstore´s warning was relating to old builds that I had deactivated on the Internal testing, closed testing tracks.

Apologies for the false alarm.

As others have reported seeing the same thing, they will likely have the same issue as me. Removing the old builds is not possible, the solution is to create a new release with a current version on each of the affected tracks. This then properly deactivates the old releases that are causing the alarm.

I think it means the best way to manage play store for avoiding this in the future, is to create new releases at the bottom level and then promote them to release once approved.


Solved here:

Let’s close this thread in favor of the linked one, as the original question was actually submitted 2 years ago here and is talking about a different version upgrade.