Jar Package Obfuscation

The jar package needs to be confused recently and there are many pits for the first time the jar is confused. First said the hole encountered, before using Eclipse packaging jar is very convenient, has not been replaced. After exporting using the Android SDK with the Proguardgui obfuscation (directory \sdk\tools\proguard\bin\proguardgui.bat) use the process online quite a lot. But because Proguardgui does not support jdk8 under the Rt.jar. Only to find the official website has been offline jdk7. The error after importing the project after the obfuscation succeeded actually reported return code 1 for Dex process. The workaround for this error on-line is that there are more than 26 classes in the inner class or one package. The effect is not visible after the modification. According to the meaning of this error, Dex turns class error. I guess is jdk7 under the Rt.java version adaptation caused, compare Proguardgui incompatible jdk8. You can only abandon eclipse using Android Studio. The focus of using Android Studio is to find Moudle compiled Classes.jar (unlike Classes.jar locations under different Android studios, most of the web is build/intermediates/ bundles/default/, and I use 3.1 in build/intermediates/packaged-classes/release/ ), use confusion relatively simple to change the buildtypes under the minifyenabled to Ture and then write Proguard-rules.pro can be confused success.

Summary: Android studio features are still a lot more powerful, note that Proguardgui has stopped maintenance.

Jar Package Obfuscation