android-studio - android studio 打包成带签名的APK报错

Question

这个错误怎么解决？

Answer 1

In many cases, the third-party SDK code is poorly written and can be ignored

Answer 2

These are Warnings, the new version of gradle will report them, and the final compilation will be successful

Answer 3

Same problem as you, the reason is dependencies {

compile fileTree(include: ['*.jar'], dir: 'libs')
//  testCompile 'junit:junit:4.12'
//compile 'com.android.support:support-v4:19.1.0'
compile 'com.android.support:appcompat-v7:23.3.0'
//   compile 'com.android.support:design:24.2.1'
//compile 'com.itextpdf:itextg:5.5.9'
compile files('libs/iTextpdf.jar')
compile files('libs/universal-image-loader-1.9.5.jar')
compile files('libs/pushservice-5.3.0.99.jar')
compile files('libs/iAppPDF.jar')

}
Here you should check the dependency issues carefully. I'll solve it.

Answer 4

The information given is too little, so I can’t confirm what the problem is

Answer 5

I just want to see if there is success in the end. If it succeeds, I don’t care. My experience is confusing configuration file issues.

Answer 6

It depends on whether it is BUILD SUCCESSFUL in the end. If so, these can be ignored. These are basically lint warnings and generally do not affect apk generation. However, there are some situations, such as FC during the running of the generated apk. You need to check the proguard configuration to see if If there is a problem with the confusion rules, make changes.

Answer 7

Although this answer is nonsense, when I encounter it, I just click Run a few times and it goes away