A TestFlight build is stuck on Missing Compliance
Missing ComplianceShort answer
Missing Compliance means App Store Connect does not know whether your build uses encryption. Answer the export compliance questions for that build under TestFlight, or add the encryption key to the app's Info.plist so every later build carries the answer. If you need export documentation, put the code Apple gives you in the plist.
Fix it fast
1Find out which cause you have
Open the build in App Store Connect and look at which button it offers. Go to Apps, pick the app, open the TestFlight tab, choose the platform under Builds, then click the build that shows Missing Compliance. Then check whether the Info.plist already has an encryption key.
grep -A1 ITSAppUsesNonExemptEncryption path/to/Info.plist2Match what you see, then jump to its fix
- 1
The build shows Missing Compliance with a Manage link beside itNobody has answered the export questions for this buildFix - 2
The same question comes back with every new build you uploadThe Info.plist has no encryption declarationFix - 3
The questions end with Go to App Encryption PageYour encryption needs export documentationFix
- 1
What does the error look like?
Missing ComplianceProvide Export Compliance InformationManage
Cause 1 of 3
Nobody has answered the export questions for this build
1Check
Only the Account Holder, Admin and App Manager roles can answer. Check that your App Store Connect role is one of them.
# App Store Connect > Users and Access > your name > Role2Fix
On the build page click Manage, or the build string, then Provide Export Compliance Information, and answer the questions. If no documentation is required, click Save.
# App Store Connect > TestFlight > Builds > [platform] > build > Manage3Verify
The build no longer shows Missing Compliance and can be given to testers.
# TestFlight > Builds: the status columnConfirmed by developer.apple.com
Cause 2 of 3
The Info.plist has no encryption declaration
1Check
Search the app target's Info.plist, or the Info tab of the target in Xcode, for the key ITSAppUsesNonExemptEncryption.
grep -rn ITSAppUsesNonExemptEncryption --include=Info.plist .2Fix
Add the key as a Boolean. Apple says to use NO when the app, including third-party libraries it links against, uses no encryption or only forms that are exempt from export compliance documentation. Otherwise use YES.
<key>ITSAppUsesNonExemptEncryption</key>
<false/>3Verify
Archive and upload a new build. It should arrive without the compliance prompt.
# Xcode > Product > Archive > Distribute App > App Store ConnectConfirmed by developer.apple.com
Cause 3 of 3
Your encryption needs export documentation
1Check
The answers say the app uses encryption that is not exempt, so Apple asks for documents.
# TestFlight > build > Manage > Provide Export Compliance Information2Fix
Click Go to App Encryption Page and upload the documents. After Apple reviews them it gives you a code. Add it to the Info.plist as a string under ITSEncryptionExportComplianceCode.
<key>ITSEncryptionExportComplianceCode</key>
<string>CODE-FROM-APPLE</string>3Verify
Upload a new build and confirm no questions are asked for it.
# TestFlight > Builds: the status columnConfirmed by developer.apple.com
How do I stop it coming back?
- Keep ITSAppUsesNonExemptEncryption in the Info.plist from the first build, so no one has to answer by hand.
- Re-check the value whenever you add a library that does its own encryption.
- Make sure at least one person with the Account Holder, Admin or App Manager role is on the release team.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Related fixes
Mobile apps
Cannot change the App Privacy answers in App Store Connect
Publish Your App Privacy Responses?
Only the Account Holder, Admin and App Manager roles can answer the App Privacy questions.
2 causes, each with a fixMobile apps
App record creation fails because you lack permission
You cannot add a new app in App Store Connect as a Developer or limited user
Only the Account Holder, an Admin or an App Manager can create an app record, and Apple blocks it until the Account Holder has signed the latest agreement.
3 causes, each with a fixMobile apps
You cannot find the button to pull your app back from review
No 'remove this version from review' message appears on the version page
There is no button called Reject Binary.
3 causes, each with a fixMobile apps
Your Apple Account cannot sign in to App Store Connect
Sign-in to App Store Connect is refused for an account that should have access
App Store Connect does not open to every Apple Account.
3 causes, each with a fixMobile apps
Apple rejected the app under Guideline 4.3, Design: Spam
Guideline 4.3(b) - Design - Spam
Guideline 4.3 is Apple's duplicate rule.
5 causes, each with a fixMobile apps
App Store Connect rejects a screenshot because it has transparency
Images can't include alpha channels or transparencies.
App Store Connect does not accept screenshots that carry an alpha channel or transparent pixels.
2 causes, each with a fix