What does Missing Compliance mean in TestFlight?

Apple’s list of build statuses describes Missing Compliance as a build that is missing export compliance documentation, with action needed. When a processed build sits in TestFlight without reaching anyone, this is often why: the export compliance question was never answered for it.

To clear it in App Store Connect, open TestFlight, choose the platform under Builds, open the build and choose Manage next to it to answer the questions, or attach documentation Apple has already approved. If your answers mean documentation is required, you upload it on the app encryption page; while Apple looks at it, the build shows Waiting for Export Compliance Review or In Compliance Review, and nothing is needed from you.

To stop it for good, answer the question in the build itself with the Info.plist key described under Export compliance; the Missing Compliance guide has the native and Expo settings.

In VibeView. A build VibeView follows never sits in Missing Compliance silently. VibeView answers from your Info.plist or the answer saved for the app; with neither, the build’s card stops at Export compliance and asks Tell us whether the app uses encryption, with No and Yes buttons. When the app does use non-exempt encryption, the card says Finish export compliance in App Store Connect and VibeView checks again on its own every 30 minutes until your documents are in. See VibeView checks again on its own.