When using ProGuard, you should be aware of a few technical issues, all of which are easily avoided or resolved:
myObject.myMethod()if that call wouldn't have any effect. It ignores the possibility that
myObjectmight be null, causing a NullPointerException. In some way this is a good thing: optimized code may throw fewer exceptions. Should this entire assumption be false, you'll have to switch off optimization using the
b.class", etc. If a package contains a large number of classes, ProGuard may also write out "
aux.class". Inconveniently, Windows refuses to create files with this reserved name (among a few other names). It's generally better to write the output to a jar, in order to avoid such problems.