If you dont want your class members to be obfuscated then use SerializedName annotation provided by Gson. For example: public class ClassMultiPoints { @SerializedName(“message”) public String message; @SerializedName(“data”) public List<ClassPoints> data; … } Moreover, make sure you do add proper proguard configuration for Gson library too. For example: ##—————Begin: proguard configuration for Gson ———- # … Read more
Make sure that the proguard file you added is NOT a Unicode text file (U+FEFF byte order mark (BOM)) as proguard will fail… Enable diag. level logging for MSBuild and get the full error message. Proguard is being replaced by Google’s R8 If you are using the latest version of Xamarin, refer to this blog … Read more
I had to add ,** to get it working. Thanks T. Neidhart! -keep class !org.apache.**,** The previous example preserved class names but still obfuscated members. So I had to add { *; }: -keep class !org.apache.**,** { *; } That’s how I obfuscate multiple packages (I have to use them all in one keep rule!) … Read more
The build process runs the tool aapt to automatically create the configuration file bin/proguard.txt, based on AndroidManifest.xml and other xml files. The build process then passes the configuration file to ProGuard. So ProGuard itself indeed doesn’t consider AndroidManifest.xml, but aapt+ProGuard do.
You shoud add a new file keep.xml under res/raw. <?xml version=”1.0″ encoding=”utf-8″?> <resources xmlns:tools=”http://schemas.android.com/tools” tools:keep=”@layout/l_used*_c,@layout/l_used_a,@layout/l_used_b*” tools:discard=”@layout/unused2″ /> In tools:keep, you list the layouts you want to keep. You can even keep specefic drawables if you use reflection in your code to get your drawable tools:keep=”@drawable/ico_android_home_infosperso” I prefer to add tools:shrinkMode=”strict” so that I make sure … Read more
For native methods: ProGuard manual > Examples > Processing native methods # note that <methods> means any method -keepclasseswithmembernames,includedescriptorclasses class * { native <methods>; } In this case, for callback methods: ProGuard manual > Examples > Processing callback methods -keep class mypackage.MyCallbackClass { void myCallbackMethod(java.lang.String); } Or e.g., if all public methods may be callback … Read more
In your Gradle file’s default configuration closure, specify your Proguard file with consumerProguardFiles instead of proguardFiles. For example: defaultConfig { consumerProguardFiles ‘proguard.txt’ }
Just add to the project’s proguard-rules: -keep public class com.google.android.gms.** -dontwarn com.google.android.gms.**
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>; }
I’ve been battling this issue for the past few hours. Basically the proguard task will halt execution if there are any warnings. You can see the Proguard warnings, and the stacktrace, by adding -d to the build (as in: gradle clean assembleRelease -d). Note that the stacktrace mentions to “Please correct the above warnings first.” … Read more