Status Update
No update yet.
Comments
se...@cebrands.ca
Great point on the regression between Merge! It’s crucial to ensure that foundational standards like ISO/IEC 27001 are added to solidify security and risk management. This certification helps organizations align with best practices, making it a vital step forward in maintaining robust data protection. Thanks for bringing that up! More Info:- https://riskprofs.com/product-category/trainings/information-security/iso-iec-27001/
je...@google.com
sp...@google.com
I was able to reproduce the issue.
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
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
Description
all required information.
Studio Build:
Version of Gradle Plugin: 3.5.0
Version of Gradle: 5.4.1
Version of Java: 1.8
OS: Windows 10
When using Build > Generate signed Bundle / APK in Android studio the resulting apk is showing as Not a signed jar file. This only seems to be affecting Wear OS builds with Gradle Plugin above 3.5.0. Lowering to Gradle Plugin 3.4.0 results in a correctly signed apk. Using keytool to validate the signed apk.
Steps to Reproduce:
1. Create new Wear OS basic application
2. In top menu select Build > Generate Signed APK
3. Create a new keystore
4. Sign with V1 and V2 signing methods (Selecting only V1 does not change results)
4. Run app-release.apk through keytool -list -printcert -jarfile .\app-release.apk
Expected Results:
Shows APK as signed, showing cert details.
Actual Results:
Shows "Not a signed jar file"