proguard

问题 I found an article which introduces the concept of randomizing the dictionary entries instead of using the standard "a, b, c, ..." for class names and variables when obfuscating. He explains that tasks can be run in gradle on build to generate a randomized text file which can replace the one provided by default: tasks.whenTaskAdded { currentTask -> //Android Gradle plugin may change this task name in the future def prefix = 'transformClassesAndResourcesWithProguardFor' if (currentTask.name

问题 Gradle ver : 3.4.1 JDK ver : 1.8 Proguard ver : 5.3.3 Android gradle plugin 2.3.+ I am getting exception in build due to proguard. I have tried proguard 5.3.2 also but with no success. Here is my release config release { debuggable false android.buildTypes.release.proguardFiles = [] proguardFile 'proguard-android.txt' //minifyEnabled shrinkResources true signingConfig = signingConfigs.release } Following is the exeption Caused by: java.lang.IllegalArgumentException: Overflow of unsigned short

问题 Gradle ver : 3.4.1 JDK ver : 1.8 Proguard ver : 5.3.3 Android gradle plugin 2.3.+ I am getting exception in build due to proguard. I have tried proguard 5.3.2 also but with no success. Here is my release config release { debuggable false android.buildTypes.release.proguardFiles = [] proguardFile 'proguard-android.txt' //minifyEnabled shrinkResources true signingConfig = signingConfigs.release } Following is the exeption Caused by: java.lang.IllegalArgumentException: Overflow of unsigned short

问题 I have built the app i release mode using proguard.and I am getting this error. 01-20 15:16:37.611: W/dalvikvm(31760): JNI WARNING: JNI method called with exception pending 01-20 15:16:37.611: W/dalvikvm(31760): Pending exception is: 01-20 15:16:37.616: W/System.err(31760): java.lang.RuntimeException: Stub When i build apk in normal way it works on my device but following release mode it does not work. 回答1: The documentation states You must not call most JNI functions while an exception is

问题 I have built the app i release mode using proguard.and I am getting this error. 01-20 15:16:37.611: W/dalvikvm(31760): JNI WARNING: JNI method called with exception pending 01-20 15:16:37.611: W/dalvikvm(31760): Pending exception is: 01-20 15:16:37.616: W/System.err(31760): java.lang.RuntimeException: Stub When i build apk in normal way it works on my device but following release mode it does not work. 回答1: The documentation states You must not call most JNI functions while an exception is

问题 In my app I send emails to some specific address, it all works fine, but when it comes to obfuscation, shrinking, etc with ProGuard it fails I've tried adding some ProGuard rules, which didn't work That's my ProGuard -keepclassmembernames class com.sun.mail.imap 2019-08-08 14:29:26.811 11724-12675/? E/AndroidRuntime: FATAL EXCEPTION: AsyncTask #5 Process: com.redegrow.besttaxi, PID: 11724 java.lang.RuntimeException: An error occurred while executing doInBackground() at android.os.AsyncTask$3

问题 I recently updated the Xamarin.Android.Support libraries from 24.2.1 to 25.3.1, so I was able to get Push Notifications to work on Android. While that made the Push Notifications work, it has now introduced an issue that only occurs when I build the project in Release mode, with ProGuard enabled. The final error is the very generic "java.exe" exited with code 1. The most meaningful I can extract from the Output window (when the Output setting has been set to Diagnostics) is Exception in

问题 I recently updated the Xamarin.Android.Support libraries from 24.2.1 to 25.3.1, so I was able to get Push Notifications to work on Android. While that made the Push Notifications work, it has now introduced an issue that only occurs when I build the project in Release mode, with ProGuard enabled. The final error is the very generic "java.exe" exited with code 1. The most meaningful I can extract from the Output window (when the Output setting has been set to Diagnostics) is Exception in

问题 As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 9 years ago . I work on a platform which runs Java apps. Those apps are often obfuscated, most of them using ProGuard, which makes debugging issues

问题 In my app I have library project dependency with lots of unused methods fields and classes. Since this is a third-party library I don't want to remove all unused classes and methods by myself due it's future updates. I'm trying to use proguard for this but -dontobfuscate will only exclude whole project from any optimisations shrinking and obfuscation. Is it possible to skip obfuscation step? 回答1: You should generally apply ProGuard to the combination of your app and its libraries. This