Typical wording
Missing Compliance — You must provide export compliance information for this build before it can be submitted for review or distributed to testers.
Common causes
- The encryption questions were never answered for this build
- The app uses HTTPS or standard platform cryptography and the developer assumed no declaration was needed
- Info.plist does not contain ITSAppUsesNonExemptEncryption, so the prompt returns for every new build
- The answer given previously does not carry over because the encryption usage changed
What to check
- App Store Connect → the build → Provide Export Compliance Information
- Whether the app only uses standard encryption (HTTPS, platform crypto) or ships its own / non-standard algorithms
- Info.plist for ITSAppUsesNonExemptEncryption
- Whether a French import declaration applies to your distribution
Fix, reply or appeal guidance
- Answer the questions on the build; for apps that only use standard encryption the declaration is usually a single answer and the build is released immediately
- Add ITSAppUsesNonExemptEncryption to Info.plist so the question stops appearing for every build — set it to the value that is true for your app
- If the app uses non-standard or proprietary encryption, prepare the documentation the regulations require (self-classification report, ERN or CCATS) before submitting
- Do not guess: the declaration is a legal statement about what the app does