Current location - Quotes Website - Signature design - The difference between app-armeabi-release.apk and app-universal-release.apk.
The difference between app-armeabi-release.apk and app-universal-release.apk.
The core difference between app-debug.apk and app-release.apk lies in AndroidManifest.xml

When app-debug.apk is generated, the compiler will automatically add Android: debug = "true" to the AndroidManifest.xml of apk.

When app-release.apk is generated, the compiler will automatically remove android:debuggable from the AndroidManifest.xml of apk..

Generate project (ctrl+F9) to generate app-debug.apk

Run app (shift+F 10) to generate app-debug.apk

Extended data:

1 and app-debug.apk can only be run to the target device by running the app. If this apk is installed to the target device through adb install, an error will be reported: Install _ failed _ test _ only 2. ADB Install can only install the released version of apk.

2. Signature of system authority:

Is the signing tool stored in the directory of system source code? out/host/Linux-x86/framework/signapk . jar

Is the signature file stored in the directory of the system source code? Build/Target/Product/Security/

Signature method: java? -Can? signapk.jar? platform.x509.pem? platform.pk8? old.apk? new.apk

3. The error of install _ failed _ shared _ user _ understood is because there is no system permission signature, that is, the permission signature is not made with platform.pk8 and platform.x509.pem.

4. The following signature in 4.android studio is not a permission signature, but a unique signature of the java package name, which is to prevent others from decompiling and tampering with the same package name. In short, there is nothing. Jks signature file, apk with the same package name cannot overwrite the installed apk with the same package name.