Google Play targets required minimum API level

Google Play enforces a minimum targetSdkVersion that advances annually. As of 2026, new app submissions require API 35 (Android 15); existing apps receiving updates require API 34. Submitting below the threshold results in an automated rejection — the Play Console shows a 'Target API level requirement not met' error before any human reviewer sees the app. This is not a lint warning; it is a hard publish block. Additionally, targeting a lower API level disables Android security features that are default-on at higher API levels: scoped storage enforcement, permission upgrade flows, and exact alarm restrictions — each of which affects real user data handling.

Update android/app/build.gradle to meet current requirements:

android {
  compileSdkVersion 35
  defaultConfig {
    targetSdkVersion 35
    minSdkVersion 24
  }
}

For Expo, set in app.json:

"android": { "targetSdkVersion": 35 }

After updating, test on an Android 15 emulator (API 35) — SDK version bumps change permission dialog flows, storage access behavior, and exact alarm scheduling. Run your existing integration tests against the new target before submitting. Document the SDK target in SUBMISSION_NOTES.md alongside the Google Play requirement version that drove the change, so the next engineer understands why the minimum exists.