Build & Compliance

Attached build & export compliance.

Source: App Store Connect.

App Encryption Declaration

ID: encryption-decl · Can be: Recommended, Passed, Error

Follows appEncryptionDeclarations on the app.

• Passed — one or more reusable declarations are on file.
• Recommended — none on file. Optional if you answer per-build, but a reusable declaration avoids answering the compliance question on every build.

Build attached

ID: build-attached · Can be: Recommended, Passed

Follows build on the version.

• Passed — a build is attached; reports its version.
• Recommended — no build attached yet. You can configure metadata now, but a processed build must be attached before submission.

Build processing state

ID: processing · Can be: Passed, Info

Reads processingState on the attached build.

• Passed — state is VALID.
• Info — any other processing state.

Export compliance

ID: export-compliance · Can be: Blocking, Passed, Error

Reads usesNonExemptEncryption on the attached build.

• Passed — the encryption answer is set.

• Blocking — usesNonExemptEncryption is null. Without it the build holds in Missing Compliance and can’t be submitted. Fastest fix is to add the Info.plist key and upload a new build:

  <key>ITSAppUsesNonExemptEncryption</key>
  <false/>

  (See the matching local check encryption-key under Xcode Project.)