Skip to content
Get a quote

App Store Connect statusTestFlight build stuck on “Missing Compliance”

The build uploaded and processed, but App Store Connect shows Missing Compliance and the build waits on you. Apple needs an answer about your app’s use of encryption for every new version, unless the answer is already in Info.plist. Here is what Apple asks for, in Apple’s words.

Short answer

Open the build in App Store Connect and answer the export compliance questions about encryption. To stop it on every upload, add the ITSAppUsesNonExemptEncryption key to Info.plist: NO if the app uses no encryption or only exempt encryption, YES if it uses non-exempt encryption, and then you typically also add the code Apple gives you after reviewing your documentation.

Why the build is held, and the fix

  1. 01

    Nobody answered the encryption questions for this build

    “Your build is missing export compliance documentation. Action is needed.” Apple, App build statuses

    Each new version waits for the export compliance answers before testers can install it. Open the build in App Store Connect and answer them; we expect the status to clear once they’re in, and if documentation is required, continue with the third cause. Apple says it’s your responsibility to review the export regulations, and that you’re responsible for liabilities from misinterpreting them or claiming exemption inaccurately.

  2. 02

    Info.plist doesn’t include the encryption key

    “App Store Connect walks you through an export compliance questionnaire every time you upload a new version of your app.” Apple, ITSAppUsesNonExemptEncryption

    Without ITSAppUsesNonExemptEncryption in Info.plist, the questions come back with every upload. Add the key as a Boolean once the answer is settled. In our experience the key only helps builds made after you add it, so upload a new build.

  3. 03

    The app needs export compliance documentation

    “Once the documentation is approved, attach it to your beta build or app version build.” Apple, Overview of export compliance

    If your answers show the app uses non-exempt encryption, such as proprietary algorithms, upload the documentation in App Store Connect. After Apple approves it, attach it to the build, and add the code Apple gives you as ITSEncryptionExportComplianceCode in Info.plist.

Checked against the vendor’s docs on : Apple: App build statuses; Apple: Overview of export compliance; Apple docs: Complying with encryption export regulations; Apple docs: ITSAppUsesNonExemptEncryption.

Rather hand it over?

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

Related: Xcode signing requires a development team · App Store Guideline 2.1 rejection

Questions

More on this error

Our app only calls APIs over HTTPS. Is that exempt?

Apple says encryption built into the operating system, for example HTTPS connections using URLSession, is typically exempt from export documentation upload requirements, and proprietary encryption is not. Apple also says it’s your responsibility to review the export regulations, so check before you answer.

Is there anything to file if our encryption is exempt?

Possibly. Apple says that if your app uses exempt forms of encryption, you might alternatively be required to submit a year-end self-classification report to the U.S. government.

Does the key cover third-party libraries?

Yes. Apple’s description of the key says the answer covers your app including any third-party libraries you link against, so check what your SDKs do before setting it.

A different error?

Describe it and get a written quote

Send the error and what you were doing. You get a written scope, a fixed price and a timeline; we reply by email, usually within one business day.

Describe your problem All fixes