The deadline
Google states that starting August 31, 2026, new mobile apps and app updates submitted to Google Play must target Android 16 (API level 36) or higher. This is not just a manifest edit: raising targetSdk can expose behavior changes, permission changes and library incompatibilities that need regression testing.
What to check first
Record the current compileSdk, targetSdk, Android Gradle Plugin, Gradle version, Kotlin version and major SDK dependencies. If the project is old, update in controlled stages instead of changing everything at once.
Common blockers
Legacy notification, background execution, storage, media, deep-linking or foreground-service behavior can surface after modernization. Third-party SDKs can also impose minimum build-tool requirements.
Submission plan
Build a release candidate, run core user journeys on Android 16 and at least one older supported Android version, verify crash reporting, then inspect the Play Console pre-launch and policy status before submitting.
When to request help
If dependency upgrades cascade into compile errors, signing problems or runtime regressions, treat the work as a modernization project rather than a quick targetSdk patch.
Official sources
Policies and platform requirements can change. Check the linked official documentation for the latest wording before acting on a time-sensitive case.
Need case-specific help?
If your situation includes a specific warning, rejection or account state, send the exact notice rather than applying generic steps blindly.
Request assessment