It should be located at build/outputs/proguard/release/mapping.txt in your application module’s directory. In the latest version of ProGuard and Android Studio, the file is located at build/outputs/mapping/release/mapping.txt.
as suggested in the comments to one of the answers above (but which i didn’t notice at first because it was buried amongst one of the “additional comments”) … we simply run progruard on the command line (see the first block below) on the library outside of eclipse with the parameters in the second block … Read more
If you’re using ADT 17 or newer, the documentation is slightly inaccurate. The generated file is proguard-project.txt and will be in the root directory of your project. To enable Proguard, you will need to ignore the “do not modify” warning in project.properties and uncomment the following line: proguard.config=${sdk.dir}/tools/proguard/proguard-android.txt:proguard-project.txt The Android toolchain will sometimes make changes … Read more
EDIT This answer is 10 years old – it may not apply to newer proguard versions. I think you need to add these flags at the very least (modify for you individual package names): -keep class javax.** { *; } -keep class org.** { *; } -keep class twitter4j.** { *; } Also, add these … Read more
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
According to the ProGuard Typical Library usage guide: The “Signature” attribute is required to be able to access generic types when compiling in JDK 5.0 and higher. Adding the following line fixed my issues with missing type parameters: -keepattributes Signature
Proguard is developed and maintained by GuardSquare while R8 is developed and maintained by Android team which means they are two different products although R8 is compatible with Proguard. As seen from here https://www.guardsquare.com/en/blog/proguard-and-r8 Compatibility of ProGuard and R8 The good news for developers is that R8 is backward compatible with ProGuard. If you have … Read more
SOLVED For others that are having this problem you need to add the following to proguard.cnf -keep public class * extends com.yoursite.android.yourappname.YourClassName -keepclassmembers class * extends com.yoursite.android.yourappname.YourClassName{ public <init>(android.content.Context); } The first keep tells proguard to not obfuscate class names that extend YourClassName The second one says to keep the constructor name (<init> means constructor) … Read more
Try this: -keep class javax.** { *; } -keep class org.** { *; } -keep class twitter4j.** { *; } Cf post from @CaspNZ: Android Proguard with external jar
If MyJavaScriptInterface is an inner class of MyClass, ProGuard expects a fully qualified name com.mypackage.MyClass$MyJavaScriptInterface. The naming convention with $ is used in the compiled class files on which ProGuard operates. Note that ProGuard mentions class names in the configuration that it can’t find in the input jar, suggesting that these names may have been … Read more