Target API Level 36: The Google Play Deadline Explained
Since August 31, 2026, Google Play apps and updates must target Android 16 (API 36). Exceptions for Wear OS, TV and Automotive, and the extension.
Short answer
Since August 31, 2026, new apps and app updates must target Android 16 (API level 36) or higher to be submitted to Google Play. Wear OS and Android Automotive OS apps need API 35+, and Android TV and Android XR apps need API 34+. Google offered an extension to November 1, 2026 through Play Console forms.
The requirement
From Google’s target API page: starting August 31, 2026, new apps and app updates must target Android 16 (API level 36) or higher, except Wear OS and Android Automotive OS apps (API 35+), and Android TV and Android XR apps (API 34+). Permanently private apps restricted to one organization are exempt.
What it means for closed testing
The requirement applies to submissions, and that includes uploads to closed testing tracks. If your build targets an older API, Play Console will block the upload or release. Fix this before you recruit testers, so your test doesn’t start late.
How to update
- In your module’s build.gradle(.kts) set targetSdk to 36 (and compileSdk to 36).
- Update the Android Gradle Plugin and dependencies. Old libraries are the most common blocker.
- Read the Android 16 behaviour changes for apps targeting 36 and test the ones that affect you.
- Run your app on an Android 16 emulator or device.
- Upload with a new version code.
For frameworks:
| Framework | Where to set it |
|---|---|
| Flutter | android/app/build.gradle(.kts), after upgrading Flutter |
| React Native / Expo | Upgrade to a version whose defaults target 36, or set via build properties |
| Unity | Player Settings → Target API Level |
| Capacitor | android/variables.gradle |
The extension
Google’s page says developers who need more time could request an extension to November 1, 2026 using forms in Play Console. If you’re reading this after that date, check the page for the current rules.
Related: Google Play requirements for new developers in 2026.
Frequently asked questions
Does it apply to my existing published app?
The requirement applies to new apps and to app updates you submit. Existing users of older versions aren’t forced to update by this rule.
What’s the difference between targetSdk and minSdk?
targetSdk tells Android which behaviour rules your app is designed for. minSdk is the oldest Android version your app installs on. Raising targetSdk doesn’t drop old devices.
Sources and how we keep this accurate
Policy facts are checked against Google's own documentation on the date shown above. Google can change requirements at any time, so confirm in your Play Console. Where we give advice or estimates rather than Google's rules, we say so. TestersZone is independent and not affiliated with Google. Drafts are AI-assisted and reviewed by our team.
Need 12 testers? Get them free.
Test 3 apps, earn 60 credits, and list your app for up to 20 real testers with verified daily check-ins.
Start freeKeep reading
Every Google Play Requirement for New Developers in 2026
How to Publish a Flutter App on Google Play (2026)
How to Publish a Unity Game on Google Play
Do Games Need the 12-Tester Closed Test Too?
“Version Code Has Already Been Used”: How to Fix It
Android Developer Verification in 2026: What Play Developers Need to Know
Browse all answers, or see the quick answers, guides and comparisons.