r8-analyzer

To find redundant ProGuard keep rules in an Android build, audit your R8 configurations to detect broad keep patterns and replace them with precise, targeted rules. This ensures safe minification and correct code retention.

The best way to narrow broad R8 keep rules is to analyze build configurations against Google's best practices, identifying safe, targeted replacements that maintain correct retention for reflection and serialization without risking misoptimization.

You need to audit your Android R8 configuration after adding a new library, encountering a release crash, or before a release. This validates that minification aligns with Android Gradle Plugin guidelines for release readiness.

Yes, R8 build optimization supports guided remediation by providing concrete rule edits and reference documentation. This guides developers through tightening configurations to ensure reliable minification and correct code retention.

An Android release crash after enabling R8 minification often happens when broad keep rules are missing or misconfigured. Analyzing your ProGuard and R8 configurations identifies these gaps and suggests precise replacements to fix retention.