If you want to make the whole build process easier for you, you should switch over to gradle and Android Studio IDE. Then you could easily add the following to your build.gradle file to run ProGuard: android { buildTypes { release { } debug { minifyEnabled true proguardFile ‘proguard-android.txt’ zipAlignEnabled true } } } This … Read more
Try adding this code to your proGuard rules, it worked for me -ignorewarnings -keep class * { public private *; } The answer was posted here: Execution failed for task ‘:app:transformClassesAndResourcesWithProguardForRelease
If you add a proguard option -printconfiguration config.txt you’ll see proguard adds -libraryjars ‘D:\tools\android\platforms\android-23\android.jar’ -libraryjars ‘D:\tools\android\platforms\android-23\optional\org.apache.http.legacy.jar’ your duplicated classes (e.g. SslError) are presented in both android.jar and org.apache.http.legacy.jar Proguard adds second jar even if you don’t useLibrary ‘org.apache.http.legacy’ Here is an open bug describing the problem. So now we can’t do anything with the issue. … Read more
Full combo of build/ clean project + build/ rebuild project + file/ Invalidate caches / restart works for me!
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
Quoting from tools.android.com: Built-in shrinker Version 2.0 of Android Plugin for Gradle ships with an experimental built-in code shrinker, which can be used instead of ProGuard. The built-in shrinker supports fast incremental runs and is meant to speed up iteration cycles. It can be enabled using the following code snippet: android { buildTypes { debug … Read more
You’re probably not actually signing the release build of the APK via the signing wizard. You can either build the release APK from the command line with the command: ./gradlew assembleRelease or you can choose the release variant from the Build Variants view and build it from the GUI:
Android SDK (r20 or higher) Please check the predefined proguard.config refered in project.properties proguard.config=${sdk.dir}/tools/proguard/proguard-android.txt More info: http://proguard.sourceforge.net/manual/examples.html#androidapplication On Gradle: buildTypes { release { minifyEnabled true shrinkResources true proguardFiles getDefaultProguardFile(‘proguard-android.txt’), ‘proguard-rules.pro’ … } } Here you can check a proguard “default” file that I keep updating: https://medium.com/code-procedure-and-rants/android-my-standard-proguard-ffeceaf65521 Android SDK (r19 or lower) You can add it … Read more
It’s likely that this is happening in the very short time frame immediately after Lollipop’s Android System WebView application updates. I’d seen this error in the Google Play Dev Console, but also had never been able to reproduce it on my Nexus 5, regardless of how much I really tried to stop my app from … Read more
org.simpleframework.xml.stream.StreamReader in your code refers to javax.xml.stream.events.XMLEvent. The latter class is part of the Java runtime (rt.jar) but not part of the Android runtime (android.jar), so ProGuard warns that something might be broken. If you’re sure that your application works anyway, you can specify -dontwarn javax.xml.stream.events.** ProGuard hell?