I ran into the same problem after adding the -dontobfuscate flag to my proguard.cfg file. The solution ended up being that I needed to add this to my optimizations: !code/allocation/variable This makes my complete optimization string look like this: -optimizations !field/removal/writeonly,!field/marking/private,!class/merging/*,!code/allocation/variable
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
I think most of those settings you have there are already included in the Android SDK by default. So you can remove most of them, just leaving in the section devoted to GSON. I am developing in Eclipse using Android SDK Tools 22.6.3 & whatever version of ProGuard ships with that. Here’s what I’m using … Read more
When you use ProGuard you have to always resolve all warnings. These warnings tell you that the libraries reference some code and there are no sources for that. That might and might not be ok. It depends if the problematic code ever get called. In this case warnings for Okio and Retrofit2 can be ignored. … Read more
Here is probably a more visual way to check. In the newer release of Android Studio, it comes with the APK Analyser that let user explore what is in the APK file and it is handy to check if your class has been obfuscated. Below image shows that both package and method name have been … Read more
add the below to your ProGuard rules -ignorewarnings -keep class * { public private *; } and rebuild your project.
Try adding -keepattributes InnerClasses -dontoptimize to the ProGuard config. That should fix the problem. It’s probable that incompatible optimizations are applied (that probably causes the last line of the error log). If you want to allow optimizations, it’s necessary to fine tune optimizations config with -optimizations optimization_filter option in ProGuard config.
Add this to ProGuard setting file(like proguard-rules.pro) -dontwarn okio.**
Try this: -keep class javax.** { *; } -keep class org.** { *; } -keep class twitter4j.** { *; } Cf post from @CaspNZ: Android Proguard with external jar