Overview — Obfuscation Pro manual

Obfuscation Pro inspects runtime entry points and keep rules for ProGuard, R8, yGuard, and Allatori. It connects source to obfuscation outputs, explains kept classes, and retraces production stack traces.

Requirements#

IDE compatibility: IntelliJ IDEA 2025.2+. Check the Marketplace list for other editions and their supported versions.

The documented release is 2026.2.2. Its Marketplace compatibility starts at IntelliJ Platform build 252.0. Check the Marketplace compatibility list for your IDE edition and version before installing.

Use a JVM or Android project with an existing obfuscator build. The plugin does not replace ProGuard, R8, yGuard, or Allatori. Generate mapping, seeds, and usage outputs where supported to enable coverage and retrace workflows.

Start here#

Install Obfuscation Pro, then follow Inspections and keep rules. The configuration reference explains where to adjust the behavior for your project.

In this manual#

Inspections and keep rules — Find fragile entry points and review precise rule fixes.
Coverage, mappings, and retrace — Explain obfuscation results and navigate production crashes.

Feature guides#

Rules and inspections#

Entry points, reflection, and precise keep rules — Choose rules that preserve both reachability and required runtime names.

Build results#

Coverage and multi-module outputs — Read kept, renamed, and shrunk states from the exact build outputs.
Mappings and production stack traces — Select a release mapping and resolve overloaded or inlined frames.

Current limitations#

Coverage reflects generated outputs and can become stale after a new build. Inspections cannot prove every dynamic reflection or runtime integration is preserved. The plugin reads and helps edit configuration; it does not execute an obfuscator or verify an application’s production behavior on its own.

Release reference#

These instructions target the published 2026.2.2 release. Check the version under Settings → Plugins → Installed if your IDE behaves differently. For setup failures, start with troubleshooting.