Analysis of R8 Class Reflection Optimization and Obfuscation Issues in Android Builds

Background: In Android projects it is common to place one‑time, context‑free initialization code (e.g., SDK init) in static blocks and trigger it via class loading, often using Class.forName("com.aaa.bbb") . The target class must be kept from obfuscation, otherwise the name may be altered.

Problem analysis: A missing keep rule caused a class name string in the compiled bytecode to be replaced by its obfuscated name, yet no ClassNotFoundException was thrown at runtime. The investigation started with documentation lookup, debugging attempts, and finally source‑code inspection.

R8 reflection optimization: R8 replaces calls to getClass() on classes without subclasses with a direct Class constant (changing an invoke‑virtual to const‑class ). This improves performance but requires the class to be resolvable, accessible and already initialized . The optimizer checks a set of “allowed” classes; if a class or any of its super‑interfaces is not in the set, the optimization is skipped.

Source‑code inspection: The relevant optimizer classes are ReflectionOptimizer , ClassRenamer , and ClassReferenceFixer . ClassRenamer creates a new string constant for the obfuscated class name and updates the constant‑pool entry. ClassReferenceFixer then rewrites all string constants that are arguments to reflection APIs (e.g., Class.forName() , Class.getDeclaredField() ) to the obfuscated name.

Findings: The problematic class implements an interface that is not part of the optimizer’s allowed set, so the reflection optimization is disabled. Consequently, the class name string is rewritten by the obfuscation step, producing the observed mismatch.

Additional observations: In AGP 8 the optimizer was relaxed; a new check based on minSdkVersion determines whether to apply the replacement, allowing more classes to be optimized.

Conclusion: The issue stems from a strict eligibility test in R8’s reflection optimizer (pre‑AGP 8) combined with the obfuscation pipeline that rewrites string literals. Understanding these internals helps avoid similar pitfalls when using static‑block initialization and reflection in Android apps.