Variable names will be obfuscated with proguard, leaving you with something like private String a; Instead of private String descripcionCategoria; You can add proguard rules so some classes don’t get obfuscated. I got away with it using these: -keepattributes Signature # POJOs used with GSON # The variable names are JSON key values and should … 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:
Library projects by themselves don’t run ProGuard, so they don’t use any configuration. Application projects obfuscate the entire code base, including any referenced libraries, so they need proper configuration for the application code and for the library code.
answer is: use this proguard.cfg ##—————Begin: proguard configuration common for all Android apps ———- -optimizationpasses 5 -dontusemixedcaseclassnames -dontskipnonpubliclibraryclasses -dontskipnonpubliclibraryclassmembers -dontpreverify -verbose -dump class_files.txt -printseeds seeds.txt -printusage unused.txt -printmapping mapping.txt -optimizations !code/simplification/arithmetic,!field/*,!class/merging/* -allowaccessmodification -keepattributes *Annotation* -renamesourcefileattribute SourceFile -keepattributes SourceFile,LineNumberTable -repackageclasses ” -keep public class * extends android.app.Activity -keep public class * extends android.app.Application -keep public class … Read more
Thank you a lot for posts like this that help us to advance step by step. I’ve came up with other solution after i have tried the last one without success: # OrmLite uses reflection -keep class com.j256.** -keepclassmembers class com.j256.** { *; } -keep enum com.j256.** -keepclassmembers enum com.j256.** { *; } -keep interface … Read more
You typically should not enable ProGuard in the library project. ProGuard processes the application and the library together in the application project, which is the most effective approach. In the library project, you can specify any library-specific ProGuard configuration in build.gradle, e.g.: defaultConfig { consumerProguardFiles ‘proguard-rules.txt’ } This file is then packaged in the library … Read more
add this: -dontwarn com.squareup.okhttp.** to your proguard-rules.pro
Although adding this to proguard-project.txt file works, it keeps all classes. -keep class com.google.android.gms.** { *; } -dontwarn com.google.android.gms.** I prefer this, which makes apk file size much smaller: -keep public class com.google.android.gms.* { public *; } -dontwarn com.google.android.gms.** Also note up to date Google Play Proguard notification here: http://developer.android.com/google/play-services/setup.html#Proguard -keep class * extends java.util.ListResourceBundle … Read more
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
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?