Repository navigation
Conversation
SnapSafe's AES-256-GCM media encryption is not exempt, so declare it in the Info.plist instead of answering per build in App Store Connect. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Up to standards ✅🟢 Issues
|
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.
Summary
ITSAppUsesNonExemptEncryption = YESinSnap-Safe-Info.plist. SnapSafe's AES-256-GCM media encryption is not exempt.CURRENT_PROJECT_VERSIONto 3 for the next upload of 1.4.0.docs/HOW-TO-RELEASE.md.Known risk: build 1 of 1.4.0 carried this same key with no
ITSEncryptionExportComplianceCodeand App Store Connect rejected the upload (altool error 90592). Unless a matching code is added, the upload after re-tagging is expected to fail the same way. CI does not exercise this check.Test plan
ITSAppUsesNonExemptEncryption = truev1.4.0🤖 Generated with Claude Code