Missing Compliance in Status when I add built for internal testing in Test Flight.How to solve?
Unless your app is using some special encryption you can simply add Boolean a key to your Info.plist with name ITSAppUsesNonExemptEncryption and 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:
- ITSAppUsesNonExemptEncryption export compliance while internal testing?
- Cannot select latest uploaded version to add to testflight
- ITSAppUsesNonExemptEncryption Cordova Build
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:
- Go to the iOS tab at the top left of TestFlight and click the yellow triangle next to the warning to provide this information within iTunes Connect:
- Click the "Provide Export Compliance Information" link in the popup:
Though, if you do choose to modify Info.plist, you'll never need to deal with this popup again.
Add following at the bottom of your Info.plist
<key>ITSAppUsesNonExemptEncryption</key>
<false/>