Coverage, mappings, and retrace

Read coverage#

Build the minified application and select its output files. Gutter icons and Project view decorations identify kept, renamed, or shrunk classes. Open the coverage tool window for a broader view and export HTML or CSV when sharing a review.

A kept class can show the matching rule and navigate to its source. Use this to find overly broad rules or explain intentional preservation. Missing or stale outputs must be corrected before treating the report as current.

Browse mappings#

Open a ProGuard/R8 mapping.txt, yGuard rename_log.xml, or Allatori log.xml in the mapping viewer. Search in either direction between original and transformed names. Select the correct module where source classes share names.

Retrace a stack trace#

Open the stack-trace retrace tool window or Analyze → Stack Trace integration. Choose the exact mapping shipped with the failing build, paste the trace, and inspect the original frames and line numbers.

The built-in parser handles overloaded and inlined mappings. If source navigation still looks wrong, compare build identity and mapping timestamps before changing parser settings. Keep production mappings with their release artifacts so later incidents can be retraced reliably.