Enable explicit v1/v2/v3 APK signing schemes on the release config#21
Merged
Conversation
The release signingConfig relied on AGP defaults, which produced a v2-only signature on directly installed APKs. Enable v1, v2, and v3 signing explicitly so the scheme set is deterministic across toolchain upgrades. At minSdk 31 apksigner reports v3 as the governing scheme and verifies with exit 0; the App Bundle path is unaffected since Google re-signs delivered artifacts. Update the signing runbook's expected apksigner output accordingly.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The release
signingConfigpreviously relied on Android Gradle Plugin defaults, which produced a v2 only signature on directly installed APKs. This enables v1, v2, and v3 signing explicitly so the scheme set is deterministic across toolchain upgrades.Detail
At
minSdk 31,apksignerreports v3 as the governing scheme and verifies with exit 0. The App Bundle path is unaffected, since Google re signs delivered artifacts with its own key. This is a compatibility hardening change ahead of the first Play Console upload, not a functional gate.Verification
:app:assembleReleaseBUILD SUCCESSFULapksigner verifyexits 0 on the signed APK:app:bundleReleaseBUILD SUCCESSFUL;jarsigner -verifyreports jar verified