I had similar problems some time ago and I solved it for me with brute force and luck. My proguard.cfg is similar, but I have lines:
-dontshrink -optimizations !code/simplification/arithmetic,!field/*,!class/merging/*
I can't remember where I got the idea for these optimization options, but they seem to work for me.
There is always a catch switch
-dontoptimize
(Indicates not to optimize input class files. By default, optimization is enabled, all methods are optimized at the bytecode level.)
which may be more appropriate.
Finally, I have methods that are only mentioned in xml files (click handlers) that should be explicitly saved using
-keepclassmembers class * extends android.app.Activity { public void myClickHandler(android.view.View ); }
Nickt
source share