Short answer
Set targetSdk (and compileSdk) to 36 in the app’s Gradle file, build, and test the screens that Android 15 and 16 change, then upload the new version. An app that doesn’t ship an update needs at least API level 35 to stay available to new users on newer Android versions. In Flutter, Expo or React Native, change it where the project sets the Android SDK versions, then check the built bundle.
What the requirement means, and the fix
01
Updates now need API level 36
“New apps and app updates must target Android 16 (API level 36) or higher to be submitted to Google Play” Google, Target API level requirements for Google Play apps
Any new upload, even a small fix, has to target Android 16. Wear OS, Android Automotive, Android TV and Android XR apps have their own levels in the same help page.
02
An older app is hidden from new users
“Existing apps must target Android 15 (API level 35) or higher to remain available to new users on devices running Android OS higher than your app’s target API level.” Google, Target API level requirements for Google Play apps
An app you haven’t updated in a while stays installed for existing users, but people on newer Android versions can’t find or install it until it targets API level 35 or higher.
03
Where to change it
“you can confirm or change the current value of targetSdkVersion in your app's Gradle file” Android Developers, Meet Google Play’s target API level requirement
Set it in the app module’s Gradle file. The code below is the Kotlin form (build.gradle.kts); in a Groovy build.gradle write compileSdk 36 and targetSdk 36 without the equals sign. Flutter projects set it in android/app/build.gradle or build.gradle.kts, Expo projects through the build properties config, and React Native projects with targetSdkVersion in the ext block of android/build.gradle. If the build then complains about the Android Gradle Plugin, update it too.
android { compileSdk = 36 defaultConfig { targetSdk = 36 } }04
Test what the new level changes
“Some of these changes only apply to apps that explicitly declare support through their targetSdkVersion manifest attribute (also known as the target API level).” Android Developers, Meet Google Play’s target API level requirement
Raising the number opts the app into each Android version’s behavior changes, which Android Developers lists per version. Run the app on an Android 15 and an Android 16 device or emulator before you upload.
Checked against the vendor’s docs on : Play Console Help: Target API level requirements for Google Play apps; Android Developers: Meet Google Play’s target API level requirement.
Rather hand it over?
Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.
- from $450App Fix TicketOne reproducible bug in an existing mobile or web app, diagnosed and fixed.See scope and start
- from $450AI-Built App RescueA Lovable, Bolt or Cursor app checked end to end in 3 days, then its worst problems fixed at a fixed price.No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.See scope and start
Related: Google Play App Bundle signed with the wrong key · Google Play version code already used · Flutter unsupported class file major version · App Store and Google Play deadlines, 2026 to 2027