Repository navigation
|
How can a team catch App does not target the current required API level automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. grep -rnE 'targetSdk(Version)?[ =]+[0-9]+' --include='*.gradle' --include='*.kts' . # must be 36 or higher from 31 Aug 2026Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. targetSdkVersion in build.gradle is below the current Google Play requirement. From 31 August 2026, new apps and updates must target Android 16, API level 36, or higher. A Play Console extension to 1 November 2026 is available. Wear OS and Automotive OS must target API 35 or higher, TV and XR API 34 or higher. The fix. Build against the current required Android target API level. From 31 August 2026 that is API 36 or higher. Submissions below the threshold are rejected automatically. Recipe source. data/detection-recipes.json This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
The quick check. Run this from the project root and read what it prints.
Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
GOOGLE-TARGET-APIwith a coverage line and a proper exit code.What the hit means. targetSdkVersion in build.gradle is below the current Google Play requirement. From 31 August 2026, new apps and updates must target Android 16, API level 36, or higher. A Play Consol…