Android Aurora Push Jpush obfuscation Solution Ultimate Article

Today in the confusion, the aurora is wrong to push the paper, the error is as follows: (The following error code from another article excerpt from, because has been resolved, will no longer show my own error message, basically is consistent, except the time. )

<span style= "FONT-SIZE:18PX;" >[2013-09-23 20:30:59-test] Proguard returned with error code 1. See console [2013-09-23 20:30:59-test] Note:there were duplicate class definitions. [2013-09-23 20:30:59-test] Unexpected error while computing stack sizes: [2013-09-23 20:30:59-test] Class = [cn/jpush/android/api/instrumen  Tedactivity] [2013-09-23 20:30:59-test] Method = [<clinit> () V] [2013-09-23 20:30:59-test] Exception = [Java.lang.IllegalArgumentException] (Stack size becomes negative after instruction [all] invokevirtual #57 in [cn/jpush/a Ndroid/api/instrumentedactivity.<clinit> () V]) [2013-09-23 20:30:59-test] Unexpected error while editing code: [ 2013-09-23 20:30:59-test] Class = [cn/jpush/android/api/instrumentedactivity] [2013-09-23 20:30:59-test] Met Hod = [<clinit> () V] [2013-09-23 20:30:59-test] Exception = [java.lang.IllegalArgumentException] (Stack si Ze becomes negative after instruction [] invokeVirtual #57 in [cn/jpush/android/api/instrumentedactivity.<clinit> () V]) [2013-09-23 20:30:59-test] Java.lang.IllegalArgumentException:Stack size becomes negative after instruction [all] invokevirtual #57 in [Cn/jpush/and Roid/api/instrumentedactivity.<clinit> () V] [2013-09-23 20:30:59-test] at Proguard.classfile.attribute.visitor.StackSizeComputer.evaluateInstructionBlock (stacksizecomputer.java:334) [ 2013-09-23 20:30:59-test] at Proguard.classfile.attribute.visitor.StackSizeComputer.visitBranchInstruction ( stacksizecomputer.java:197) [2013-09-23 20:30:59-test] at proguard.classfile.instruction.BranchInstruction.accept ( branchinstruction.java:140) [2013-09-23 20:30:59-test] at Proguard.classfile.attribute.visitor.StackSizeComputer.evaluateInstructionBlock (stacksizecomputer.java:355) [ 2013-09-23 20:30:59-test] at Proguard.classfile.attribute.visitor.StackSizeComputer.visitCodeAttribute0 ( stacksizecomputer.java:153) [2013-09-23 20:30:59-test] AT Proguard.classfile.attribute.visitor.StackSizeComputer.visitCodeAttribute (stacksizecomputer.java:110) [ 2013-09-23 20:30:59-test] at Proguard.classfile.editor.StackSizeUpdater.visitCodeAttribute (Stacksizeupdater.java : +) [2013-09-23 20:30:59-test] at Proguard.classfile.editor.CodeAttributeEditor.visitCodeAttribute0 ( codeattributeeditor.java:376) [2013-09-23 20:30:59-test] at Proguard.classfile.editor.CodeAttributeEditor.visitCodeAttribute (codeattributeeditor.java:311) [2013-09-23 20:30:59-test] at Proguard.optimize.DuplicateInitializerInvocationFixer.visitCodeAttribute ( duplicateinitializerinvocationfixer.java:92) [2013-09-23 20:30:59-test] at Proguard.classfile.attribute.CodeAttribute.accept (codeattribute.java:101) [2013-09-23 20:30:59-test] at Proguard.classfile.ProgramMethod.attributesAccept (programmethod.java:79) [2013-09-23 20:30:59-test] at Proguard.classfile.attribute.visitor.AllAttributeVisitor.visitProgramMember (Allattributevisitor.java: [2013-09-23 20:30:59-test] at Proguard.classfile.util.SimplifiedVisitor.visitProgramMethod ( simplifiedvisitor.java:91) [2013-09-23 20:30:59-test] at proguard.classfile.ProgramMethod.accept ( programmethod.java:71) [2013-09-23 20:30:59-test] at proguard.classfile.ProgramClass.methodsAccept ( programclass.java:504) [2013-09-23 20:30:59-test] at Proguard.classfile.visitor.AllMethodVisitor.visitProgramClass (allmethodvisitor.java:47) [2013-09-23 20:30:59-test] at proguard.classfile.ProgramClass.accept (programclass.java:346) [2013-09-23 20:30:59-t EST] at proguard.classfile.ClassPool.classesAccept (classpool.java:116) [2013-09-23 20:30:59-test] at Proguard.op Timize. Optimizer.execute (optimizer.java:500) [2013-09-23 20:30:59-test] at Proguard. Proguard.optimize (proguard.java:306) [2013-09-23 20:30:59-test] at Proguard. Proguard.execute (proguard.java:115) [2013-09-23 20:30:59-test] at Proguard. Proguard.main (proguard.java:492) </span> 

Baidu all kinds of solutions on the Internet, after trying n times still invalid, the last colleague to his confused files all replaced, and not simply a jar file, and finally the perfect solution.

Here's a quick solution:

1. add code to your proguard.cfg: If you are using the new version of ADT Project.Properties the "# proguard.config=${sdk.dir}/ Tools/proguard/proguard-android.txt:proguard-project.txt "#" comment is removed and then configured in Proguard-android.txt as follows:

-dontwarn cn.jpush.**
-keep class cn.jpush.** {*;} < /span>

2. using sdk1.3.x and later versions

3. Replace the Proguard folder point in D:\adt-bundle-windows-x86-20130729\sdk\tools I immediately download the latest version of the confusion file

So, it is perfect to solve the problem of Jpush confusion error.

Android Aurora Push Jpush obfuscation Solution Ultimate Article