Closed pekspro closed 1 year ago
The problem is you are using keytool
which can be used to verify JAR signatures on APK file. Try using apksigner
tool for APKs: https://developer.android.com/studio/command-line/apksigner.
Only legacy APK v1 signature has JAR-compatible format. This scheme is deprecated and replaced with a new APK signature scheme v2 starting Android 7. Because your radiostorm
app has minSdk = 24 the legacy v1 signature (JAR-compatible) is not generated for your APK.
Thanks, @ymakhno, I'm very greatful to have an explanation of this. I suspected I messed up something 😄
Describe the bug I have been redirected from this issue: https://github.com/dotnet/maui/issues/10872
TLDR; I have two MAUI-applications where I have created AAB files. I want to convert these to signed APK-files. This works for one of the applications, but the other will be an unsigned APK-file. The commands I use are identical.
Bundletool version(s) affected Version: 1.12.1 (and older versions too).
Stacktrace No visible errors, no stacktrace.
To Reproduce Download this file that contains the aab-files: https://pekspro.com/files/aab_to_apk_test.zip
Create a certificate, use password 12345678:
Run this on the first application. It will say that the generated APK-file is signed:
Compare this we the second application. The APK-file will be unsigned.
Expected behavior Both APK-files should be signed. Or, if something is corrupt, we should get an error message.
Known workaround No workaround found.
Environment: OS: Windows 10, 21H1
I noticed the problem when I was building my application via GitHub actions.