r8-analyzer

Overly broad R8 keep rules can prevent code shrinking by preserving unnecessary classes and members. An R8 keep-rule audit applies an impact hierarchy to detect subsuming rules and library-consumer redundancies that block the shrinker from removing code.

To find redundant Proguard keep rules, run an R8 keep-rule audit that evaluates your configuration in a structured order. The audit checks for library-consumer redundancies and applies an impact hierarchy to identify subsuming rules that unnecessarily preserve code.

Narrowing R8 keep rules safely requires proposing reflection-aware, targeted rules instead of broad preservation. An audit flags reflection-driven scenarios and recommends validating changes via UI testing to ensure reflection-dependent code remains functional.

Troubleshooting R8 not removing code requires inspecting Gradle build files and keep rules for overly broad preservation. An audit checks R8 release optimization settings and identifies subsuming rules that prevent effective code shrinking.

Checking gradle.properties is required before optimizing R8 shrinking to confirm release optimization and resource shrinking settings are configured correctly. A configuration review inspects these build files to ensure the environment supports effective code removal.

You should not use broad keep rules when they subsume narrower rules and block code shrinking. An R8 audit detects subsuming rules and library-consumer redundancies, proposing reflection-aware alternatives that preserve only what is required.