Android Target API 36 Migration: Roadmap Before August 31, 2026

What changes with target API 36

Target API upgrades are not only store compliance work. They can change runtime behavior, permission handling, background execution, notifications, privacy boundaries and compatibility with native modules.

For React Native and Expo projects, the migration also depends on the Android Gradle Plugin, compile SDK, native dependencies and build pipeline.

Migration roadmap

1. Inventory the current build

Record the current `targetSdkVersion`, `compileSdkVersion`, Gradle version, Android Gradle Plugin version, React Native or Expo SDK version and native packages.

2. Upgrade in a branch

Do not start with production. Create a migration branch, update SDK settings and resolve build errors before touching release workflows.

3. Test affected behavior

Focus on permissions, push notifications, background work, deep links, file access, camera, location, billing and authentication redirects.

4. Validate store readiness

Check Play Console warnings, internal testing tracks, release notes and crash reports before the final rollout.

Business impact

Missing the target API deadline can block updates, delay campaigns and increase emergency maintenance cost. A planned migration is cheaper than a last-week store compliance sprint.