Fix: ITSAppUsesNonExemptEncryption Prompt in TestFlight

Fix: ITSAppUsesNonExemptEncryption Prompt in TestFlight
Quick answer: If your app uses no encryption or only encryption that qualifies for an exemption, add the Boolean key ITSAppUsesNonExemptEncryption to its Info.plist and set it to NO. If the app uses non-exempt encryption, set the key to YES and complete any export compliance steps Apple requires. You can also upload a build without the key and answer the compliance questions in App Store Connect.

Why this happens

TestFlight can ask for export compliance information when you select a build for internal testing. Apple needs to know whether the app uses encryption that requires additional export compliance review. This can happen even though the build has uploaded successfully.

ITSAppUsesNonExemptEncryption is an optional Boolean property in the app’s Info.plist. It tells App Store Connect whether the app uses non-exempt encryption. A value of NO means the app either uses no encryption or uses only encryption that qualifies for an exemption. It does not mean that every form of encryption is absent from the app.

The key is not a universal bypass for the compliance questions. Its value must describe the app accurately, including encryption used by code and dependencies you ship. If you are unsure whether an exemption applies, review Apple’s current export compliance guidance and seek appropriate advice before declaring NO.

How to fix it

1. Set the Boolean to NO when your app qualifies

If you have determined that your app uses no encryption, or only exempt encryption, add ITSAppUsesNonExemptEncryption to the app target’s Info.plist with a Boolean value of NO.

To edit a plist file directly:

  1. Open the Info.plist used by your app target in Xcode.
  2. Add a new property using the raw key ITSAppUsesNonExemptEncryption.
  3. Set its type to Boolean and its value to NO.
  4. Create and upload a new build, then select that build in TestFlight.

In the plist’s XML source, the property looks like this inside the existing <dict> element:

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

The <false/> element is the plist representation of Boolean NO. Do not enter the word NO as a string: the property should be a Boolean.

If your project uses Xcode’s generated Info.plist rather than a separate plist file, add the property through the app target’s Info settings. In either setup, verify that it appears in the built app’s Info.plist before uploading. Changing a local project setting does not alter a build that is already in App Store Connect.

2. Declare non-exempt encryption accurately

If your app uses non-exempt encryption, use Boolean YES instead:

<key>ITSAppUsesNonExemptEncryption</key>
<true/>

Then complete the applicable export compliance questions in App Store Connect. Depending on the app and its encryption, Apple may require documentation and review. Setting the value to YES is a declaration, not a substitute for those requirements.

Check the entire shipped app when making the determination. Encryption can come from your own implementation, a framework or an included third-party SDK. The fact that a dependency handles encryption for you does not, by itself, establish whether the app qualifies for an exemption.

Avoid choosing a value solely to make the prompt disappear. If the classification is unclear, use Apple’s current questions and documentation to assess the app’s actual use of encryption.

3. Answer the questions without adding the key

The key is optional. You can upload a build without ITSAppUsesNonExemptEncryption and provide the requested export compliance information in App Store Connect instead.

This can be useful when you are still determining the correct declaration or do not want to change and upload a new build just to add the property. Select the build for TestFlight and follow the export compliance prompts shown for it. Answer based on the app’s actual encryption use; omitting the key does not remove the obligation to answer accurately.

If Apple requires supporting documents, submit them through the export compliance area in App Store Connect. Required documents must be reviewed and approved before the app can be distributed for prerelease testing. Allow for that review when planning a TestFlight rollout.

4. Use an Apple-provided compliance code only when applicable

There is a separate Info.plist property, ITSEncryptionExportComplianceCode, for a code associated with export compliance documentation. It is not the same as the ITSAppUsesNonExemptEncryption Boolean.

If your app needs documentation, follow the instructions in App Store Connect to provide it. When Apple supplies a code for the applicable documentation, include that value as directed. Do not invent a code or substitute the Boolean value for it. A code referencing documentation does not make an unapproved document approved; Apple’s review requirements still apply.

Apps that do not need an export compliance code can be uploaded without one. Similarly, the absence of either key does not necessarily mean the upload will fail; App Store Connect can ask for information after the upload.

5. Check the archived app if the prompt persists

If you added the Boolean but still see the prompt, first confirm that you selected the newly uploaded build. A previously uploaded build retains the Info.plist with which it was built.

Then inspect the archive you uploaded:

  1. In Xcode, locate the archive in the Archives organizer and reveal it in Finder.
  2. Open the archive’s package contents and find the app under Products/Applications.
  3. Inspect the app’s Info.plist and look for ITSAppUsesNonExemptEncryption.
  4. Confirm that the value is a Boolean and matches your compliance determination.

For example, you can inspect a plist from Terminal by replacing the path below with the path to the archived app’s plist:

plutil -p "/path/to/YourApp.app/Info.plist"

If the property is missing or has the wrong value, check that you edited the app target’s configuration rather than a different plist or target. Correct the configuration and upload another build. If the value is correct but App Store Connect still requests information, complete the applicable questions rather than assuming the declaration satisfies every review requirement.

How to prevent it

  • Decide how the app’s encryption is classified before preparing a TestFlight build.
  • Recheck the declaration when adding or changing an SDK or encryption feature.
  • Keep the property as a Boolean, not a string.
  • Verify the archived app’s Info.plist when changing build settings or targets.
  • Allow time for documentation review if Apple requires it.

FAQ

Is ITSAppUsesNonExemptEncryption required for internal TestFlight builds?

No. You can upload a build without the key and answer the export compliance questions in App Store Connect. Required compliance review can still affect whether the build is available for testing.

Does NO mean my app cannot use HTTPS?

No. NO can also describe an app that uses only encryption qualifying for an exemption. Determine whether the app’s actual encryption use qualifies rather than assuming the answer from the presence or absence of HTTPS alone.

Will adding the key update a build already uploaded to TestFlight?

No. The property is included in the app at build time, so upload a new build to change its value. For an existing build, use the compliance questions available in App Store Connect.

Sources & credits

Parts of this guide are adapted from content licensed under CC BY-SA 3.0; this article is shared under the same license.