From the literal meaning of the V4 packet repeatedly caused by the error, thought this simple, so in the app's Libs view, delete, because I am using the form of online compilation
So look under the dependency tree
Find V4 packages in almost every project
Google found a method after
Compile (' your package ') {
exclude group: ‘com.android.support‘, module: ‘support-v4‘
}
The meaning of this method is: The V4 package is excluded when compiling the package
Found no use
Then find a way in the overflow
configurations { all*.exclude group: ‘com.android.support‘, module: ‘support-v4‘ all*.exclude group: ‘com.android.support‘, module: ‘support-annotations‘ }
found that even the V4 of the project itself had been ruled out, no
after searching for a long time without a solution, I decided to take an exclusionary approach.
first create a new project, in the new project to introduce all the Moudule, signature, found through, so that the problem of moudule itself is excluded,
Since the basis sent a general direction after the application itself to troubleshoot, first of all, I use the type of import to the Libs of the jar are imported so save the trouble of repeated import every time
Compile Filetree (include: [' *.jar '], dir: ' Libs '),
After a long repetition of finding a v13 bag,
Google later found that this was
Android-support-v13 is a version compatible package that is released by Google, with a minimum compatible Android3.2 system. It was designed to develop a flat plate. Android 3.x systems are tablet-only systems, but the 3.x system has failed. So using V13 's package has no value.
Turns out this is not the equivalent of V4, then decisively deleted
Android Studio signed APK when you encounter error Building android apk-duplicate V4 widget