Parse wrapped Linux apksigner output - #15
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
22 tasks
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
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.
What changed
Makes the updater's exact APK signer parser tolerate PowerShell 7's Linux native-command/ErrorRecord and ANSI rendering around otherwise valid
apksigner --print-certsoutput.The parser still requires the exact
Signer #N certificate SHA-256 digest:label, exactly 64 hex characters, successfulapksignerexit status, and the downstream exact-one-signer check.Root cause
Signed prerelease run
31727479600built and verified the signed APK successfully, but the extracted-bundle PowerShell verifier did not recognize the extensionless Linuxapksigneroutput because the rendered line may have a PowerShell prefix/control sequences. Packaging stopped before release publication.Validation
No release or assets were published by the failed run. The existing tag remains recorded at the failed source commit until this fix is reviewed and merged; tag replacement will be explicitly audited before rerun.