r8-analyzer

To find redundant Proguard keep rules that bloat your Android release APK, analyze your build configuration and R8 keep rules by checking library redundancies and broader subsuming rules. This structured diagnosis isolates overly broad preservation rules blocking code shrinking.

The impact hierarchy for classifying R8 keep rules prioritizes library redundancy first, then evaluates impact levels, and finally checks subsuming or broader rules. This structured classification order identifies which rules can be safely removed or refined to improve shrinking.

To fix R8 shrinking issues when your app uses reflection, detect likely dynamic-loading scenarios within affected packages and apply narrow keep rules tailored to the specific reflection usage. This targeted refinement prevents overly broad preservation while maintaining runtime functionality.

Yes, this R8 analyzer works with your AGP version and build.gradle.kts files by inspecting build.gradle or build.gradle.kts and gradle.properties. It verifies whether R8 and resource shrinking are enabled correctly for your specific AGP version.

The best way to reduce app size by narrowing keep rules is to generate a per-rule remediation plan that prioritizes removal or refinement by codebase impact hierarchy. This produces concise actions and recommends targeted UI Automator testing to verify changes.

Your R8 configuration analysis recommends removing certain keep rules because they are redundant with library-provided rules or are subsumed by broader existing rules. Removing these unnecessary rules unblocks the shrinking process and reduces final release bundle size.