Menu
When I added my latest build for internal testing with TestFlight, I saw that it had a "Missing Compliance" status.
Is this a major problem? Why does this appear? How can I resolve this issue?
303
To add Internal testers: Navigate back to your app in My Apps, select the TestFlight tab and click Internal Testing on the left-hand side; Now click the (+) sign next to the header Internal Testers; Check the box next to any eligible users who have not already been invited and click Add.
To distribute using TestFlight or through the App Store, choose App Store Connect. If you are a member of the Apple Developer Enterprise Program and are ready to release your app to users in your organization, choose Enterprise. To distribute a macOS app without code signing, choose Copy App.
Download TestFlight app and start testing Invited testers will receive an email with a link to test your app. To be able to test, they will first have to download the TestFlight app. After accepting the invitation, they will be directed to the TestFlight app and they will be prompted to install to app to be tested.
It means that the app uses no encryption, or only exempt encryption. If your app uses encryption and is not exempt, you must set this value to YES/true. Very few apps can set this to NO; for example if any part of your app uses https you almost certainly need to say YES.
Unless your app is using some special encryption you can simply add Boolean a key to your Info.plist with name ITSAppUsesNonExemptEncryption and value false.
In code:
<key>ITSAppUsesNonExemptEncryption</key> <false/> If you want to use the Xcode UI instead, head over to the Project > Target > Info panel, add a new "App Uses Non-Exempt Encryption" Boolean key with value NO:
If your app is using custom encryption then you will need to provide extra legal documents and go through a review of your encryption before being able to select builds.
If you continue with selecting that version for testing, it will ask for the compliance information manually. Choosing "No" presents you with the plist recommendation above.
This is change has been announced in the 2015 WWDC, but I guess it has been enforced only very recently. See this and this for a transcript of the WWDC session related to the export compliance, just to a text search for "export".
There are other similar questions on SO, see:
78
There's no longer any need to submit a new build or modify Info.plist; instead, follow these steps using an Admin or App Manager account:
Though, if you do choose to modify Info.plist, you'll never need to deal with this popup again.
24
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
