When using Proguard with Android, methods that are only invoked via reflection (e.g., callbacks defined in onClick XML attributes) are erroneously stripped out.
One solution for this issue is to add each affected class and method to your proguard.cfg.
How can I use Java annotations to achieve the same effect?
I feel that would make the code self-documenting and it would avoid code and proguard.cfg drifting out of sync. However, Android's Proguard doesn't seem to ship with the annotations.jar mentioned in its documentation.
-keepclassmembernames. This is the most permissive keep directive; it lets ProGuard do almost all of its work. Unused classes are removed, the remaining classes are renamed, unused members of those classes are removed, but then the remaining members keep their original names.
Specifies not to shrink the input. By default, ProGuard shrinks the code: it removes all unused classes and class members. It only keeps the ones listed by the various -keep options, and the ones on which they depend, directly or indirectly.
You can retrieve annotations.jar
and annotations.pro
from an official ProGuard release. You should then be able to use annotations as discussed here
All the necessary options can go in proguard.cfg.
I ran in to this problem recently. Here is what you need to do:
To fix the onClick events add this to Proguard settings
-keepclassmembers class * extends android.app.Activity{
public void *(android.view.View);
}
To keep annotation add
-keepattributes **
or -keepattributes *Annotation*
More information is available here http://www.simpligility.com/2010/12/hints-for-using-proguard-on-your-android-app/ I use maven-android-plugin to compile android app and this article pretty much sums up what I do for the android to get it working. Hope this helps!
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With