Repository navigation
|
How can a team catch Release build not optimized, shrunk, or obfuscated 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 -rqE '(isMinifyEnabled|minifyEnabled)[[:space:]=]+true' --include='*.gradle' --include='*.kts' .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 What the hit means. From February 2027 apps must be optimized with a minimum of 25 percent coverage across optimization, shrinking, and obfuscation using a tool such as R8. A release build with minifyEnabled false, or with no minifyEnabled at all, falls below the bar and loses visibility and publishing capabilities. The fix. Enable R8 in the release build type (isMinifyEnabled = true, isShrinkResources = true), fix keep rules, and verify the Play Console optimization report before February 2027. 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
ANDROID-R8-OPTIMIZATION-MISSINGwith a coverage line and a proper exit code.What the hit means. From February 2027 apps must be optimized with a minimum of 25 percent coverage across optimization, shrinking, and obfuscation using a tool such as R8. A release build with minifyEnabled fal…