Made a few changes to proguard-project.txt file (if you have more than one module in your project – put it in the module which calls the *.jar file you are getting warned about): -keepattributes SourceFile,LineNumberTable -keep class com.parse.*{ *; } -dontwarn com.parse.** -dontwarn com.squareup.picasso.** -keepclasseswithmembernames class * { native <methods>; } The -dontwarn lines were … Read more
ProGuard manual > Examples > Producing useful obfuscated stack traces The SourceFile attribute is required, because Oracle/Sun’s Java virtual machine otherwise does not include line numbers in stack traces, which is what you really want (and which is quite harmless on its own). I haven’t checked if this is true for Android’s Dalvik virtual machine. … Read more
According to ProGuard documenation the wildcard <fields> matches any field. Thus it should be something like: -keepclassmembers class com.tools.app.holiday.Holiday { private <fields>; } If you want to preserve private fields in all classes use: -keepclassmembers class * { private <fields>; }
As of Guava 17.0, this is what I needed in ProGuard config: -dontwarn javax.annotation.** -dontwarn javax.inject.** -dontwarn sun.misc.Unsafe Otherwise build fails with warnings like: Warning: com.google.common.base.Absent: can’t find referenced class javax.annotation.Nullable (That’s because Guava uses annotations that are not part of Android runtime (android.jar). In this case it’s fine to just mute the warnings.) If … Read more
If MyJavaScriptInterface is an inner class of MyClass, ProGuard expects a fully qualified name com.mypackage.MyClass$MyJavaScriptInterface. The naming convention with $ is used in the compiled class files on which ProGuard operates. Note that ProGuard mentions class names in the configuration that it can’t find in the input jar, suggesting that these names may have been … Read more
Yes, by specifying -dontshrink -dontoptimize You can find details on all configuration options in the ProGuard manual. Note that shrinking and optimization may help preventing reverse engineering a bit.
Possibly a ‘proguard.cfg’ problem. Does it include any ‘-injars’? If your project includes another project as a library, jars can be processed twice. Could you post your ‘proguard.cfg’? Extract from http://proguard.sourceforge.net/index.html#manual/troubleshooting.html: Your input jars contain multiple resource files with the same name. ProGuard continues copying the resource files as usual, skipping any files with previously … Read more
SOLVED For others that are having this problem you need to add the following to proguard.cnf -keep public class * extends com.yoursite.android.yourappname.YourClassName -keepclassmembers class * extends com.yoursite.android.yourappname.YourClassName{ public <init>(android.content.Context); } The first keep tells proguard to not obfuscate class names that extend YourClassName The second one says to keep the constructor name (<init> means constructor) … Read more
So, Why do I see that much increase in my app size, Can it be minimized? Almost solely because of your res folder images! You should have around 4 copies of each image in the drawable-mdpi, -hdpi, xhdpi folders. The only difference is that theu are all different sizes. Is it safer to delete them, … Read more
Add this line to your proguard-project.txt file. # will keep line numbers and file name obfuscation -renamesourcefileattribute SourceFile -keepattributes SourceFile,LineNumberTable https://www.guardsquare.com/en/products/proguard/manual/usage