Optimizer removes handler for NoClassDefFoundError
Java class file shrinker, optimizer, obfuscator, and preverifier
Brought to you by:
guardsquare
Gerald Rosenberg reports that the optimizer sometimes erroneously removes a handler for a NoClassDefFoundError (forum/182456/topic/3786380). Example:
try {
return object instanceof SomeClass;
} catch (java.lang.NoClassDefFoundError e) {
.....
}
The problem can be solved by adding the following line in
src/proguard/optimize/info/ExceptionInstructionChecker.java, at line 126:
case InstructionConstants.OP_INSTANCEOF:
This fix will be included in the next (beta) version of ProGuard.