One of the most common friction points developers encounter when uploading an iOS build to App Store Connect or TestFlight is the "Missing Compliance" yellow warning badge.
When this occurs, Apple halts distribution: the build cannot be installed by internal or external TestFlight testers, and it cannot be selected as a release candidate for App Store review until the compliance status is resolved.
Developers searching for a quick fix often encounter forum posts suggesting they blindly paste <key>ITSAppUsesNonExemptEncryption</key><false/> into their Info.plist. While this clears the warning for applications that legitimately qualify, doing so without evaluating your application's actual cryptographic usage can violate United States Export Administration Regulations (EAR) and Apple Developer Program terms.
This guide explains the regulatory and technical background of Apple's export compliance checks, provides a practical decision framework for evaluating cryptographic usage, outlines when you must answer questions in Apple's web portal versus updating your source configuration, and shows how to audit compliance blockers using your AI coding assistant.
Why Apple Enforces Export Compliance Declarations
Apple's servers and the App Store are headquartered in the United States. Under US Export Administration Regulations (EAR Category 5, Part 2), software that incorporates cryptographic algorithms is considered dual-use technology subject to federal export controls.
When you upload an application archive (.ipa) to Apple, Apple's automated binary ingestion pipeline scans your compiled Mach-O executable for cryptographic symbols (such as CommonCrypto, CryptoKit, OpenSSL, or custom encryption libraries).
Because modern mobile applications routinely use encryption—such as standard TLS/HTTPS through networking libraries like NSURLSession, AlamoFire, or Flutter http—Apple requires an official declaration regarding whether the encryption is exempt or non-exempt.
Evaluating Cryptographic Usage: Practical Decision Framework
Before changing any configuration files, you must evaluate whether your application qualifies for an exemption under U.S. export law:
[Does your app use cryptography?]
│
No ────────────┴──────────── Yes
│ │
(No encryption) ▼
│ [Does it ONLY use standard OS encryption,
│ HTTPS/TLS network calls, authentication,
│ or standard password protection?]
│ │
│ Yes ───────────┴─────────── No
│ │ │
▼ ▼ ▼
[ITSAppUsesNonExemptEncryption = false] [ITSAppUsesNonExemptEncryption = true]
Exempt from US Reporting Requires Statutory Documentation / BIS
1. What Generally Qualifies as Exempt Encryption (<false/>)
Under US EAR regulations (specifically Note 4 to Category 5, Part 2, and License Exception ENC § 740.17(b)(1)), most standard consumer mobile applications qualify for exemptions. An application is generally exempt if its cryptographic usage is limited to:
- Standard HTTPS / TLS / SSL: Securing network API requests, web views, or backend communications.
- Operating System Primitives: Utilizing Apple's built-in platform APIs for authentication (e.g., Touch ID / Face ID via
LocalAuthentication, securing tokens in the iOS Keychain). - Standard Digital Signatures & Hashing: Verifying download integrity via SHA-256 or MD5.
- Standard Platform DRM: Decrypting local game assets or digital media using standard operating system features.
If your application exclusively uses encryption for these standard purposes, you generally qualify for an exemption and can legitimately declare ITSAppUsesNonExemptEncryption = false.
2. When Encryption Is Non-Exempt (<true/>)
Your application likely utilizes non-exempt encryption if it implements:
- Custom or Proprietary Cryptography: Custom mathematical encryption algorithms or non-standard ciphers not standardized by NIST or recognized international standards bodies.
- Point-to-Point Messaging Encryption: Specialized end-to-end encrypted messaging systems that bypass standard platform TLS/HTTPS networking.
- Specialized Cipher Suites: Cryptographic mechanisms designed for non-mass-market, defense, or specialized security applications outside standard consumer operating system boundaries.
If your application utilizes non-exempt encryption, setting ITSAppUsesNonExemptEncryption = false is legally non-compliant. Setting this key to <true/> alerts Apple's ingestion pipeline that your app uses non-exempt cryptography, prompting Apple to evaluate required regulatory documentation.
3. Critical Regulatory Qualifications
Developers must understand the following statutory boundaries:
- HTTPS does not guarantee universal exemption: If your application uses HTTPS for networking but also implements custom encrypted local storage or proprietary messaging ciphers, the presence of HTTPS does not exempt the rest of the application.
- Keychain usage is not an automatic shield: Storing keys in the Keychain is an OS primitive, but if the data protected by those keys is encrypted with non-standard ciphers, statutory obligations still apply.
- Different ciphers have different filing requirements: Software using non-exempt mass-market encryption may qualify for distribution subject to an Annual Self-Classification Report to the Bureau of Industry and Security (BIS), whereas restricted or defense-grade algorithms may require a formal Commodity Classification (CCATS) determination from BIS (§ 740.17(b)(2)/(b)(3)). Foreign jurisdictions (such as France's ANSSI) may also impose regional declarations.
- Setting
<false/>does not resolve non-exempt software: Merely settingITSAppUsesNonExemptEncryptiontofalsein code does not legally satisfy underlying export compliance if your software actually uses non-exempt cryptography.
No Legal Certification: This guide describes Apple's technical ingestion keys and portal questionnaires. It does not provide legal advice, classify encryption algorithms, or replace counsel from a qualified export compliance attorney. FlightDeck does not provide statutory compliance certification. Developers are legally responsible for evaluating their software against official BIS regulations (bis.doc.gov).
Resolving the Blocker: Uploaded Builds vs. Future Builds
How you resolve the warning depends on whether you need to fix a build that is already uploaded or prevent the warning on future builds.
Scenario A: Unblocking an Already-Uploaded Build
If you already uploaded a build and it is stuck in "Missing Compliance" in App Store Connect, modifying your local source code will not unblock it because the uploaded binary cannot be modified on Apple's servers.
To unblock the current build without re-compiling:
- Log in to App Store Connect.
- Navigate to Apps > Your App > TestFlight > iOS.
- Locate the build displaying the yellow Manage or Provide Export Compliance Information warning.
- Click Manage to open the compliance questionnaire.
- Answer the prompts truthfully: - "Does your app use encryption?" Select Yes if it uses HTTPS/TLS. - "Does your app qualify for any exemptions?" Select Yes if it meets the exemption criteria outlined above.
- Click Save. The build will immediately transition to
Ready to Testand release to your internal TestFlight groups.
Scenario B: Preventing the Warning Permanently in Source Code
To avoid manually answering the questionnaire in the web portal every time you push an update, declare the compliance status directly in your project configuration.
Configuring ITSAppUsesNonExemptEncryption Across Frameworks
Once you have verified that your app qualifies for an exemption, embed the declaration into your project configuration.
1. Native iOS (Swift / Objective-C)
Open your project's Info.plist and add:
<key>ITSAppUsesNonExemptEncryption</key>
<false/>
If using Xcode's modern build system without an explicit Info.plist file, navigate to your target's Build Settings > Info.plist Values, add a key named App Uses Non-Exempt Encryption, and set its value to NO.
2. Flutter
In your Flutter project, open ios/Runner/Info.plist and insert the key inside the top-level <dict> block:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>ITSAppUsesNonExemptEncryption</key>
<false/>
...
</dict>
</plist>
3. React Native and Expo
For bare React Native projects, edit ios/YourAppName/Info.plist. For Expo managed projects, configure app.json:
{
"expo": {
"ios": {
"config": {
"usesNonExemptEncryption": false
}
}
}
}
Once this key is embedded into your compiled binary, Apple's ingestion servers automatically read the value during processing, skipping the manual compliance questionnaire and immediately releasing the build to TestFlight.
Auditing Compliance Blockers with Your AI Coding Assistant
You can ask your AI coding assistant to inspect your project for cryptographic usage and audit App Store Connect release blockers before making configuration changes.
Step 1: Source Inspection and Advisory Prompt
Before modifying project configuration, prompt your assistant to examine your codebase:
Inspect our iOS project dependencies and source code for cryptographic libraries or custom encryption usage. Explain what encryption is present, whether it appears limited to standard HTTPS/TLS and OS primitives, and advise me on whether our application qualifies for ITSAppUsesNonExemptEncryption = false before making any changes.
Your assistant will examine your package manifests (Podfile, Package.swift, pubspec.yaml, package.json) and source imports, highlighting whether standard networking libraries or specialized cryptographic packages (such as libsodium or custom ciphers) are present.
Step 2: Pre-Flight Readiness Inspection Prompt
Ask your assistant to audit your App Store version before submitting for review:
Run a release readiness check on App Store Connect version [e.g., 1.0.0] for [Your App Name]. Tell me if export compliance or any other prerequisites are blocking submission.
Your assistant uses FlightDeck to inspect the version and attached build. If export compliance is unresolved, FlightDeck reports a BLOCKED status:
- The build number lacking compliance.
- The specific blocker reason (
EXPORT_COMPLIANCE). - Instructions on resolving the blocker in the App Store Connect portal or in
Info.plist.
Step 3: Recording a Local Compliance Attestation
For corporate compliance and team audit logs, FlightDeck allows you to record a local, factual attestation:
Record an export compliance attestation in FlightDeck for [Your App Name]. Note that our cryptographic usage is restricted to standard HTTPS/TLS and iOS Keychain storage under US EAR Note 4 to Category 5 Part 2, verified by engineering on [date].
Internal Audit Log Only: FlightDeck records internal compliance attestations locally for engineering audit trails. Recording an attestation does not dispatch API mutations to Apple or automatically clear Apple's server-side export compliance blocker. Statutory declarations must be completed directly in Apple's web portal or embedded into your binary's property list.
Summary Checklist and Next Steps
| Checkpoint | Action Required | Interface |
|---|---|---|
| 1. Cryptography Audit | Review networking and auth code to verify exemption status. | Code Review / AI Prompt |
| 2. Stuck Uploaded Build | Answer compliance questionnaire for that specific build. | App Store Connect Web |
| 3. Future Builds | Add ITSAppUsesNonExemptEncryption: false to project config. |
Local Project Config |
| 4. Pre-Flight Verification | Verify build has transitioned to VALID and is not blocked. |
Conversational AI prompt |
| 5. Team Audit Record | Record local factual attestation for corporate release log. | FlightDeck local audit log |
Related Resources
- Apple Developer: Overview of Export Compliance
- Apple Developer: Complying with Encryption Export Regulations
- Pre-Upload Binary Inspection: How FlightDeck Validates .ipa Files
- Why Is My TestFlight Build Stuck on Processing? Causes and Fixes
- Uploading React Native and Expo IPAs to App Store Connect with AI