In TestFlight, what does a build's Missing Compliance status mean, and how do you stop later builds of the app hitting it?
answer
- export rules, not App Review
- questions answered per build
- previously approved documentation
- a key in the app's Info.plist
- ITSEncryptionExportComplianceCode from Apple
basics
~20 sMissing Compliance means the build has no export compliance answer for its encryption use. Answer the questions or attach approved documentation in TestFlight; declaring encryption use in Info.plist with ITSAppUsesNonExemptEncryption stops each new build asking.
solid answer
~40 s**Missing Compliance** means App Store Connect has no export compliance information for the build's use of encryption, and action is needed. You fix that build in the TestFlight tab: open it, then either answer the export compliance questions under **Provide Export Compliance Information** or upload previously approved documentation with **Choose File**. If documentation is required, you upload it on the App Encryption page and Apple gives you a key value to enter in Xcode. To stop every new build asking again, declare it in the app's `Info.plist`: `ITSAppUsesNonExemptEncryption` states whether the app uses non-exempt encryption, and `ITSEncryptionExportComplianceCode` carries the code Apple issued. Statuses such as **Waiting for Export Compliance Review** need no action from you.
code
plaintext · 3 lines// Release.xcconfig
// Only for an app that uses no non-exempt encryption.
INFOPLIST_KEY_ITSAppUsesNonExemptEncryption = NOgo deeper
Recognise Missing Compliance as an export compliance question about encryption, not a review rejection or a crash.
Explain both fixes: answering or attaching documentation for one build, and declaring the Info.plist keys so later builds skip the questions.
Keep beta rounds from stalling by putting the declaration in the target's settings, and tell compliance statuses apart from Not Available for Testing.
Treat the encryption declaration as a legal statement the team owns, decided once and reviewed when the app's use of encryption changes.
## What the status means Every build uploaded to App Store Connect has to say whether, and how, it uses **encryption**, because US export rules cover software that contains it. When a build arrives without that answer, TestFlight shows the build status **Missing Compliance**: the build is missing export compliance documentation and **action is needed**. This is not TestFlight App Review and not a crash or signing problem; it is a declaration the team has not made yet. Whether a given app's encryption is exempt, and whether documentation is needed, is a legal determination covered by Apple's guide to cryptography and US export compliance. The engineer's part is making sure every build carries the answer the team decided on. ## Where it sits in the beta flow TestFlight's own overview puts the question at the upload step: after you upload a build, you read the cryptography and export compliance guidance to decide whether you need to provide app encryption documentation. So the question meets every new build at upload. For a team that uploads several builds a day, the cost is not the answer itself but the person who has to give it each time: a nightly build keeps the status Missing Compliance until someone with the Account Holder, Admin or App Manager role clicks through. The help page describes the `Info.plist` declaration as removing the need to answer the encryption questions "with each app submission", which is what turns a daily chore into a one-time decision. ## Fixing the build in front of you You need the Account Holder, Admin or App Manager role. 1. In the app's **TestFlight** tab, under *Builds*, choose the platform. 2. In the *Build* column, click the build that is missing compliance information. 3. Either click **Manage** beside it and then **Provide Export Compliance Information** to answer the required questions, or click **Choose File** to upload documentation that was approved before. 4. If the answers show that **app encryption documentation** is required, click **Go to App Encryption Page** and upload it. Apple then provides a key value to enter in Xcode, which removes the need to answer the questions with each submission. 5. If documentation is not required, click **Save**. ## Stopping every new build asking Answering by hand on every upload is the usual way a beta round stalls. The help page's fix is to declare the encryption settings in the app's `Info.plist` in Xcode, which "eliminates the need to answer encryption questions with each app submission". Two keys are involved: - `ITSAppUsesNonExemptEncryption`: whether the app uses **non-exempt** encryption. An app that uses no encryption, or whose encryption is exempt, declares that here. - `ITSEncryptionExportComplianceCode`: Xcode's *App Encryption Export Compliance Code*, the place for the **key value Apple provides** after you upload encryption documentation. With `GENERATE_INFOPLIST_FILE` on, Xcode writes both keys from build settings, `INFOPLIST_KEY_ITSAppUsesNonExemptEncryption` and `INFOPLIST_KEY_ITSEncryptionExportComplianceCode`, so the declaration can live beside the target's other settings. ## The compliance statuses | Status | What it asks of you | |---|---| | Missing Compliance | act: answer the questions or attach documentation | | Waiting for Export Compliance Review | nothing: documentation was submitted and is in review | | In Compliance Review | nothing: documentation is in review | Two statuses look similar but have other causes: - **Not Available for Testing**: the provisioning profile is missing an application identifier, and the fix is a new build that includes it. - **Invalid Binary**: the upload did not meet the upload requirements, and the fix is to resolve the issue and deliver again. ## A routine that keeps builds moving 1. Decide once, with whoever owns legal questions, whether the app uses non-exempt encryption. 2. Put that answer in the target's `Info.plist`, directly or through the build setting. 3. If documentation is needed, upload it once and add the key value Apple provides. 4. Revisit the answer when a new feature or library adds encryption. ## What goes wrong - Setting `ITSAppUsesNonExemptEncryption` to `NO` just to silence the questions turns a legal statement into a convenience setting; the value has to match what the app really does. - Answering per build without adding the key means every build of every beta round stops at Missing Compliance until someone with the right role clicks through. - Waiting for the status to clear itself does not work; Missing Compliance stays until someone gives the answer. The build settings mechanism, and how Xcode merges generated keys into the final `Info.plist`, are covered with Xcode; the status, what it blocks and how TestFlight lets you answer it belong here.
- Your app does need encryption documentation; how do you keep later builds from asking again?Upload the documentation on the App Encryption page in App Store Connect. Apple then provides a key value to enter in Xcode; put it in the app's Info.plist as ITSEncryptionExportComplianceCode, alongside ITSAppUsesNonExemptEncryption, and later builds carry the answer instead of stopping at Missing Compliance.
- A build shows Waiting for Export Compliance Review; should you resubmit it?No. That status means the documentation was submitted and is being reviewed, and the help page says no action is needed. Resubmitting does not speed it up; wait for the review to finish.
- Missing Compliance clears by itself once the build finishes processing.
- Missing Compliance can only be fixed by uploading a new build.
- Export compliance matters only at App Store submission, not for betas.
- Set ITSAppUsesNonExemptEncryption to NO on every app to skip the questions.
- Waiting for Export Compliance Review means you must answer the questions again.