Status Update
No update yet.
Comments
uc...@google.com
Not reproduced, both the scenarios app-debug.apk is not signed.
je...@google.com
sp...@google.com
This appears to be a duplicate of
V1 signing is not needed if minSdkVersion is >= 24. If you need a V1 signature for some reason, a possible workaround could be to set minSdkVersion to 23 and/or wait for a fix for
V1 signing is not needed if minSdkVersion is >= 24. If you need a V1 signature for some reason, a possible workaround could be to set minSdkVersion to 23 and/or wait for a fix for
Description
Gradle version:
5.4.1
Android Plugin Version:
3.5.2
Module Compile Sdk Version:
29
Module Build Tools Version:
29.0.2
Android SDK Tools version:
Installed, version is not shown
Steps to reproduce:
1. Open AndroidStudio and create a new project via the wizard (empty activity)
2. Run the debug version of the app via AndroidStudio
3. Under the hood gradle will be used to build "app-debug.apk" which will be installed and run
4. This APK file is however not signed. This can be verified by running the following command: keytool -list -printcert -jarfile app-debug.apk. This command will result in the following out: Not a signed jar file
When the app is build directly via the commandline (via ./gradlew assembleDebug) the APK file will be signed with the debug keystore. The keytool command can be used to verify this and will result in the following output (truncated):
Signer #1:
Signature:
Owner: CN=Android Debug, O=Android, C=US
Issuer: CN=Android Debug, O=Android, C=US
Serial number: 5a0d7315
[....]
The APK is also signed correctly when I downgrade the Android Plugin version to 3.4.2.