chore(mobile): declare non-exempt encryption usage in Info.plist#1474
Merged
Conversation
The Flutter app implements NIP-44 v2 (ChaCha20 + HMAC-SHA256 + HKDF via pointycastle, secp256k1 ECDH) in-app rather than using Apple's OS encryption, so ITSAppUsesNonExemptEncryption must be true. Setting the key here answers the export compliance prompt up front so TestFlight and App Store submissions aren't blocked per build. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
Sets
ITSAppUsesNonExemptEncryptiontotruein the iOSInfo.plistfor App Store export compliance.The Flutter app implements NIP-44 v2 encryption in-app (
mobile/lib/shared/crypto/nip44.dart: ChaCha20 + HMAC-SHA256 + HKDF viapointycastle, plus secp256k1 ECDH) rather than relying solely on Apple's OS encryption. Per Apple's export compliance rules, that makes the app's encryption non-exempt, so the key must betrue. All algorithms are published standards (IETF/SECG), so the app classifies as mass-market 5D992.c under License Exception ENC §740.17(b)(1) — no CCATS or document uploads required; the remaining compliance answers are given once in App Store Connect.Setting the key in the plist answers the encryption prompt up front so TestFlight and App Store submissions aren't blocked per build.
Test plan
🤖 Generated with Claude Code