r8-analyzer

To find redundant R8 keep rules blocking APK shrinking, audit keep directives by evaluating impact hierarchy and subsuming patterns, identifying overly broad package-wide rules that prevent code removal. This generates prioritized removal instructions without modifying keep files.

Tightening Proguard keep rules for reflection requires identifying where reflection drives the need for kept classes, then guiding toward narrower, scenario-specific rules in affected packages. This reflection-driven refinement produces a safer final rule set.

R8 troubleshooting applies across Gradle Groovy and Kotlin DSL build files, inspecting build.gradle or build.gradle.kts and gradle.properties to target AGP/R8 optimization misconfigurations and incorrect keep-rule patterns.

R8 keep rules subsume others when overly broad package-wide patterns encompass narrower directives, blocking optimization. Auditing rules via impact hierarchy classification reveals subsuming patterns and generates precise refinement guidance to resolve the issue.

Review build.gradle and gradle.properties settings for R8 shrink optimization misconfigurations by inspecting AGP/R8 optimization flags, ensuring effective project configuration for safe code shrinking and optimization.

R8 keep rule analysis for APK size reduction is limited to inspecting build configuration and classifying keep rules without modifying keep files, providing removal or refinement instructions that users must manually apply to ensure safety.