You don’t specify in what way it doesn’t work. Your configuration keeps the names of all public classes in the specified package: -keep public class com.myapp.customcomponents.* The following configuration keeps the names of all public classes in the specified package and its subpackages: -keep public class com.myapp.customcomponents.** The following configuration keeps the names of all … Read more
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.
I find a far easier solution is to forget all the if checks all over the place and just use ProGuard to strip out any Log.d() or Log.v() method calls when we call our Ant release target. That way, we always have the debug info being output for regular builds and don’t have to make … Read more
As it is, your compiled application contains the key strings, but also the constant names APP_KEY and APP_SECRET. Extracting keys from such self-documenting code is trivial, for instance with the standard Android tool dx. You can apply ProGuard. It will leave the key strings untouched, but it will remove the constant names. It will also … Read more
1. How can I completely avoid reverse engineering of an Android APK? Is this possible? AFAIK, there is not any trick for complete avoidance of reverse engineering. And also very well said by @inazaruk: Whatever you do to your code, a potential attacker is able to change it in any way she or he finds … Read more