Current location - Quotes Website - Personality signature - Pit trip with signature error "Installation analysis failed without certificate"
Pit trip with signature error "Installation analysis failed without certificate"
The last normal debugging installation, the library was added, the gradle file was modified, and then the signature verification failed with the following error:

Analysis: the preliminary judgment is related to the signature method, but generally the keyStore file is not specified. In debugging state, users \ xxx.android \ debug.keystore under the system disk is used by default, and only dependencies are added in the modified gradle file, but the related signature configuration is not modified;

Analysis: Many brothers said that after Android7.0, they used a new signature method, packaged it just in case, checked both methods, and then manually configured the signature of debug, indicating that there are both signature methods. Why is it invalid? Look at the source code: (It turns out that these two values are true by default, and there is no need to set them at all)

Analysis: I am really confused here. It stands to reason that Android6 mobile phone is not good, and it is normal to be higher than 6. It really should be related to the signature method, and there is nothing I can do. ...

Analysis: It is related to the added dependency package. Looking back, I only added Mqtt-related dependencies, and there were no redundant actions. It suddenly occurred to me that a higher version of the mobile phone seemed to throw an exception. At that time, I was bent on solving the signature problem and ignored it. Looking back:

Analysis: this is unusual. I have to check it quickly:

The reason is that some documents such as. RSA,。 DSA and. SF is caused by repeated references to some dependencies after maven is packaged, and this exception will be thrown when running Jar. Most solutions are to delete these files in the jar, so the packaging configuration is modified:

1 and V 1(JAR) signatures need to sign all files in apk, and V2 scheme is to sign all files in APK; Similarly, a verification signature is installed. V 1 requires hash verification for all files, while V2 only needs to verify it once.

2.V 1 only guarantees the integrity of each file in the Apk compressed package, but not the integrity of the whole package. V2 can guarantee these two points.

3. For projects with more files, V2 is obviously faster than V 1 in the two processes of packaging, installation and analysis.