
You upload a new iOS build, it finishes processing, and TestFlight shows Missing Compliance next to it instead of letting testers install it. This TestFlight missing compliance status means App Store Connect is waiting for you to say whether the app uses encryption. You can answer by hand every time, or add one key, ITSAppUsesNonExemptEncryption, to Info.plist and never see it again. This post shows how to pick the right value, add it to a Flutter or native project, fix builds that are already stuck, and make CI refuse to upload a build without it.
Quick answer
TestFlight marks a build Missing Compliance when its Info.plist has no ITSAppUsesNonExemptEncryption key and nobody has answered the export compliance questions for it. Answer the questions once in App Store Connect. If the result is "no documentation required" (typical for an app that only uses HTTPS through Apple's networking APIs), add ITSAppUsesNonExemptEncryption set to NO (false) to Info.plist. If Apple approved encryption documentation for you, set it to YES and add ITSEncryptionExportComplianceCode with the code Apple gave you.
What this means for your app or business
This is not a rejection and nothing is wrong with your app. It is a paperwork step. But it costs real time: every build sits in TestFlight until someone with the Account Holder, Admin or App Manager role logs in and clicks through the questions. If your release depends on a CI pipeline uploading builds at night, testers wake up to a build they can't install.
- Cost of the fix: about 15 minutes for a typical app, plus a one-line CI check. It only gets bigger if the app ships its own encryption and needs documents approved, which Apple says takes about two business days when the information is complete.
- Risk: the answer is a legal statement about US export rules, and Apple says you carry the liability if you claim an exemption wrongly. Don't guess. Pick the value from the questionnaire result, not from a forum post.
- When to get help: if your app adds its own encryption (end-to-end messaging, an encrypted database, a VPN, custom crypto), or you sell in France, it's worth having a developer and possibly an export adviser look at it before release.
Why does TestFlight say Missing Compliance?
Apple's Complying with Encryption Export Regulations page explains the background. When you upload to TestFlight or the App Store, the build goes to a server in the United States, so distributing it outside the US and Canada counts as an export under US law, wherever your company is based. If the app uses, contains or calls any encryption, App Store Connect needs an export compliance answer for it.
There are two ways to give that answer:
- Answer the questions in App Store Connect for each build.
- Put the answer in Info.plist with
ITSAppUsesNonExemptEncryption, so App Store Connect reads it on upload.
The ITSAppUsesNonExemptEncryption reference says that without the key, App Store Connect walks you through the questionnaire every time you upload a new version. In TestFlight that shows up as the Missing Compliance status, which Apple's build status table describes as "Your build is missing export compliance documentation. Action is needed."
| Build status | What it means | What you do |
|---|---|---|
| Missing Compliance | No export compliance answer for this build | Answer the questions or add the Info.plist key |
| Waiting for Export Compliance Review | Documents submitted, waiting for Apple | Nothing, wait |
| In Compliance Review | Apple is reviewing your documents | Nothing, wait |
| Ready to Submit | Compliance done | Add testers or submit for review |
Which value should ITSAppUsesNonExemptEncryption have?
Apple's export compliance documentation table gives three cases:
| Encryption your app uses | Documents in App Store Connect | Info.plist |
|---|---|---|
| Only encryption inside Apple's OS (for example HTTPS through URLSession) | None | ITSAppUsesNonExemptEncryption = NO |
| A standard algorithm not provided by the OS | French encryption declaration, only if you distribute in France | Follow the questionnaire result |
| Proprietary algorithms not accepted by standards bodies | US CCATS and the French declaration | YES plus ITSEncryptionExportComplianceCode |
The documentation page says to set the key to NO when the app, including any third-party libraries it links against, uses no encryption or only exempt encryption. That library part matters. Check the SDKs in your Podfile.lock, Package.resolved or pubspec.lock for anything that bundles its own crypto, such as an encrypted local database, an end-to-end encryption library or a VPN SDK.

What about Flutter apps?
Most Flutter apps I work on only talk to their own backend, Firebase or a payment API over HTTPS. One detail is worth knowing: Flutter's dart:io HttpClient does not go through URLSession, and the Dart team has an open documentation issue (since 2020) about which TLS libraries dart:io uses on each platform. If you want HTTPS on iOS to go through Apple's own networking stack, use cupertino_http (3.1.1 at the time of writing), which wraps Apple's Foundation URL Loading System behind the normal package:http Client. Either way, standard TLS is a standard algorithm, not proprietary crypto, so it never puts you in the CCATS row of the table. Answer the questionnaire honestly and use its result.
How do I fix Missing Compliance for good?
Step 1: Answer the questions once
In App Store Connect, open the app, go to App Information, and click the add button next to App Encryption Documentation. You can also click Manage next to the stuck build on the TestFlight tab, as Apple's beta builds guide describes. The result tells you whether documents are needed. That unblocks the current build.
Step 2: Add the key to Info.plist
For a Flutter app, edit ios/Runner/Info.plist and add this inside the top-level <dict>:
<key>ITSAppUsesNonExemptEncryption</key>
<false/>In Xcode, the same key appears in the Info tab as App Uses Non-Exempt Encryption. If Apple approved documents for your app, use this instead, with the code shown next to your approved documentation in App Store Connect:
<key>ITSAppUsesNonExemptEncryption</key>
<true/>
<key>ITSEncryptionExportComplianceCode</key>
<string>PASTE-THE-CODE-FROM-APP-STORE-CONNECT</string>On Expo, set ios.config.usesNonExemptEncryption in app.json (see the Expo app config reference), which writes the same key at build time.
Step 3: Fix builds that are already stuck
The new key only helps builds you upload after the change. For builds already marked Missing Compliance, either click through the questions per build or use the App Store Connect API. Apple's Modify a build endpoint accepts usesNonExemptEncryption on PATCH /v1/builds/{id}. This script lists recent builds of one app that have no answer yet and, with --apply, sets them to false. Only run it if false is the correct answer for your app.
#!/usr/bin/env python3
"""Answer export compliance for TestFlight builds that are still unanswered.
Only use this when ITSAppUsesNonExemptEncryption = false is the correct answer
for your app. Requires: pip install pyjwt cryptography requests
"""
import os, sys, time
import jwt, requests
API = "https://api.appstoreconnect.apple.com/v1"
def token() -> str:
with open(os.environ["ASC_KEY_PATH"]) as f: # the AuthKey_XXXX.p8 file
key = f.read()
now = int(time.time())
return jwt.encode(
{"iss": os.environ["ASC_ISSUER_ID"], "iat": now, "exp": now + 15 * 60,
"aud": "appstoreconnect-v1"},
key, algorithm="ES256",
headers={"kid": os.environ["ASC_KEY_ID"], "typ": "JWT"},
)
def main() -> int:
dry_run = "--apply" not in sys.argv
s = requests.Session()
s.headers["Authorization"] = f"Bearer {token()}"
r = s.get(f"{API}/builds", params={
"filter[app]": os.environ["ASC_APP_ID"], # numeric Apple ID of the app
"filter[expired]": "false",
"fields[builds]": "version,processingState,usesNonExemptEncryption",
"sort": "-uploadedDate",
"limit": 50,
}, timeout=30)
r.raise_for_status()
for b in r.json()["data"]:
a = b["attributes"]
if a.get("usesNonExemptEncryption") is not None or a.get("processingState") != "VALID":
continue
print(f"build {a['version']} ({b['id']}): no export compliance answer yet")
if dry_run:
continue
p = s.patch(f"{API}/builds/{b['id']}", json={"data": {
"type": "builds", "id": b["id"],
"attributes": {"usesNonExemptEncryption": False}}}, timeout=30)
p.raise_for_status()
print(" set usesNonExemptEncryption = false")
if dry_run:
print("Dry run only. Re-run with --apply to update these builds.")
return 0
if __name__ == "__main__":
sys.exit(main())The token follows Apple's Generating tokens for API requests rules: ES256, your key ID in the header, the issuer ID, the appstoreconnect-v1 audience and a lifetime under 20 minutes. Use a team API key with the App Manager role or higher.
Step 4: Make CI refuse builds without the key
A teammate can delete the key during a merge, or a new target can ship without it. This guard fails the pipeline before upload, on any macOS runner:
#!/usr/bin/env bash
# Fail the CI build early if Info.plist has no export compliance answer.
set -euo pipefail
PLIST="${1:-ios/Runner/Info.plist}"
if ! value=$(/usr/libexec/PlistBuddy -c "Print :ITSAppUsesNonExemptEncryption" "$PLIST" 2>/dev/null); then
echo "error: ITSAppUsesNonExemptEncryption is missing from $PLIST" >&2
echo "TestFlight will mark this build Missing Compliance." >&2
exit 1
fi
echo "ITSAppUsesNonExemptEncryption = $value"
if [ "$value" = "true" ] && ! /usr/libexec/PlistBuddy -c "Print :ITSEncryptionExportComplianceCode" "$PLIST" >/dev/null 2>&1; then
echo "error: value is true but ITSEncryptionExportComplianceCode is not set" >&2
exit 1
fiSave it as scripts/check_export_compliance.sh and call it before the build in GitHub Actions:
name: ios-testflight
on:
push:
tags: ["v*"]
jobs:
build:
runs-on: macos-15
steps:
- uses: actions/checkout@v4
- name: Check export compliance key
run: bash scripts/check_export_compliance.sh ios/Runner/Info.plist
- uses: subosito/flutter-action@v2
with:
channel: stable
- run: flutter build ipa --release
# signing and upload steps followOn Codemagic or Bitrise, run the same script as the first script step. If signing is what keeps breaking in your pipeline, my posts on the GitHub Actions "No signing certificate" error and the Apple Distribution certificate limit cover those parts.
How do I verify the fix?
- Run the guard script locally on a Mac: it should print
ITSAppUsesNonExemptEncryption = false(or true with a code). - After
flutter build ipa, check the built app, not just the source file:/usr/libexec/PlistBuddy -c "Print :ITSAppUsesNonExemptEncryption" build/ios/archive/Runner.xcarchive/Products/Applications/Runner.app/Info.plist. - Upload the next build. When processing finishes it should go straight to Ready to Submit (or be available to internal testers) without the Missing Compliance status.
- Run the API script without
--apply. It should list no new builds.
How do I stop it coming back?
- Keep the key in version control in the main target's Info.plist.
- Keep the CI guard as a required step before any upload.
- Re-check the answer whenever you add an SDK that does its own encryption, or start selling in France.
- When you use approved documents, store the compliance code with your release notes so the next developer knows where it came from.
Missing Compliance often shows up in the same week as other upload surprises. If your build also failed with ITMS-91061, see the missing privacy manifest fix, and if App Review comes back asking for details, see Guideline 2.1 Information Needed.
Frequently asked questions
What does Missing Compliance mean in TestFlight?
It means App Store Connect has no export compliance answer for that build. Apple's build status reference says action is needed: answer the encryption questions for the build or provide the answer in Info.plist.
How do I get rid of Missing Compliance permanently?
Answer the export compliance questions once, then add the ITSAppUsesNonExemptEncryption key to your app's Info.plist with the value that matches the result. App Store Connect reads it on every upload and stops asking.
Should ITSAppUsesNonExemptEncryption be NO or YES?
Set it to NO if the app, including its third-party libraries, uses no encryption or only exempt encryption, such as HTTPS through Apple's own APIs. Set it to YES with ITSEncryptionExportComplianceCode if Apple approved encryption documentation for your app.
Does using HTTPS count as encryption for App Store export compliance?
Yes, HTTPS is encryption, but Apple says encryption built into the operating system, such as HTTPS through URLSession, is typically exempt from documentation upload requirements. Answer the questionnaire to confirm your case.
Where do I add ITSAppUsesNonExemptEncryption in a Flutter app?
Add it to ios/Runner/Info.plist inside the top-level dict, as a key followed by false or true. In Xcode it appears in the Runner target's Info tab as App Uses Non-Exempt Encryption.
Does adding the key fix builds that are already uploaded?
No. The key only affects new uploads. For builds already marked Missing Compliance, answer the questions per build in App Store Connect or set usesNonExemptEncryption on each build with the App Store Connect API.
How long does Apple take to review encryption documentation?
Apple says it expects to review and clear complete export compliance submissions in about two business days, then gives you a code to put in ITSEncryptionExportComplianceCode.
Do I need a French encryption declaration?
Only if you distribute in France and your app uses encryption beyond what Apple's operating system provides. Apple's documentation table lists it for standard algorithms not provided by the OS and for proprietary algorithms.
Sources
- Complying with Encryption Export Regulations (Apple Developer Documentation)
- ITSAppUsesNonExemptEncryption (Apple Developer Documentation)
- Overview of export compliance (App Store Connect Help)
- Export compliance documentation for encryption (App Store Connect Help)
- Determine and upload app encryption documentation (App Store Connect Help)
- Provide export compliance information for beta builds (App Store Connect Help)
- App build statuses (App Store Connect Help)
- Modify a build (PATCH /v1/builds/{id}) (Apple Developer Documentation)
- List builds (GET /v1/builds) (Apple Developer Documentation)
- Generating tokens for API requests (Apple Developer Documentation)
- Document which encryption libraries are used for HTTPS calls (issue #41467) (dart-lang/sdk on GitHub)
- cupertino_http (pub.dev)
- app.json / app.config.js reference (Expo Docs)
Keep reading
- ITMS-91061 Missing Privacy Manifest in Flutter: How to Fix ItGot ITMS-91061 after uploading a Flutter iOS build? Find the SDK Apple names, upgrade Flutter, plugins and pods, and verify the IPA before re-uploading.
- Guideline 2.1 Information Needed: How to Get ApprovedWhat App Store Guideline 2.1 Information Needed asks for on a new app, how to reply without a new build, and how it differs from App Completeness.
- Apple Distribution Certificate Limit: Fix It in CI/CDFix the Apple Distribution certificate limit in CI: free a slot safely, then make fastlane, GitHub Actions or Codemagic reuse one shared certificate.
Comments
Share a question or note about this article.
Loading comments…