Repository navigation
Declare no non-exempt encryption in both Info.plist files - #222
Merged
Merged
Conversation
App Store Connect asks the export compliance question for each build until the Info.plist answers it. The answer is always "None", so the key gives that answer and new builds are ready to submit. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_018omeoU3hAmLQVupznzKcNk
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.
🤖 Generated with Claude Code
Each new build lands in App Store Connect as "Missing Compliance", and we answer "None of the algorithms mentioned above" by hand. This PR sets
ITSAppUsesNonExemptEncryptiontofalseinconfigs/full/Info.plistandconfigs/lite/Info.plist, so new builds are ready to submit without that step.