Workaround: Skip receipt authenticity check DO NOT MERGE
#92
Conversation
This file contains 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
schwmi
changed the title
Workaround: Skip receipt authenticity checkWorkaround: Skip receipt authenticity check DO NOT MERGE
weichsel
approved these changes
Aug 28, 2023
|
Actual fix in the making: #93 |
|
Actual fix merged. |
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.
Probably due to https://developer.apple.com/documentation/technotes/tn3138-handling-app-store-receipt-signing-certificate-changes# the call to
SecKeyVerifySignaturethrows and error and leads to a receipt validation error.This PR temporarily disables the call (for shipping a hot fix) until we implement a replacement for
SecKeyVerifySignature.