Android App Obfuscation, packaging, error log tracking

A dozen confusing packages, with formal signatures

1 Edit the Proguard-rules.txt file, configure a class or method that cannot be confused, or you will get an error.

A. code that needs reflection

B, System interface

C, JNI interface

D. Code that requires serial number and deserialization (that is, JavaBean that implements the serializable, parcelable interface)

E. JavaBean for metadata interaction with the server (JSON, corresponding classes in XML)

2 Check the Buildtypes release node in the Gradle.build file to confirm minifyenabled true

3 Turning off log printing in the Logutils tool class

4 can execute Gradle clean assemblerelease package directly inside the command line with AS

5 found./build/outputs/apk/xxx-release.apk

Note Back up the mapping file./build/outputs/mapping/release/mapping.txt

Second, through the mapping file to view the confusion after the error problem:

1, go to the Android SDK directory sdk/tools/proguard/bin/proguardgui.sh Drag this file to the command line, so you can go to a graphical interface operation.

2, retrace--> Import the Mapping.txt file, paste the error log from the crash collector file into the obfuscated stack trace, then click retrace! button, so you can see the code before the confusion, positioning the bug of course!

Android App Obfuscation, packaging, error log tracking