Missing Compliance Status in Testflight

Missing Compliance status in TestFlight

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:

Screenshot of the Xcode view where to add the value.

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.

iTunes Connect encryption export compliance alert for testing

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

Missing compliance in upload date status in new group testflight when i add the build to test how to i solve this

There's another way no need to submit a new build or modify Info.plist if you start Internal Testing ASAP without Uploading new build.

Note : If You will modify Info.plist, you'll never need to deal with this popup again.

You can simply 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:

Below is the screen shot for the same :

Sample Image

Then click the "Provide Export Compliance Information" link in the popup & Select No And Start Internal Testing :

Sample Image

Cannot provide missing compliance for testflight

I don't know why this happened in the first place, but this solved my issue:
Missing Compliance in Status when i add built for internal testing in Test Flight.How to solve?

Simply adding NO to ITSAppUsesNonExemptEncryption in Info.plist and then uploading the build again did the job.

EDIT
Eventually, together with my team mates, we understood this is a matter of restrictions, as my user on itunes connect did not have the right authority level.

Missing export compliance information - iTunes Connect/TestFlight

As I found myself, for the first issue user role doesn't matter. What you have to there is go inside you build and "Provide Export Compliance Information". There you have to provide security information regarding your app. Once you finished answering the questions you will be able to start internal testing.

This build is missing export compliance information.

You need to add this to the plist to remove that alert from itunes

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

answer is NO

App Store - Help answering Missing Compliance (using Expo + Firebase)

Question 1:

Reply YES as you use HTTPS encryption for connections

Question 2:

For what you said about your app the reply is NO. In brief you don't use any function inside your app that use a custom cryptography or it's strictly medical app. The encryption that you use it's only for data passing from app to server, nothing inside your app is encrypted (app or a part/module of app is not encrypted).

Question 3:

No you don't use a custom crypt algorithm. That is usually used for bank app data inside the app.

Question 4:

Say NO. The US rules give an exception for apps with only HTTPS calls (that is what you do). Read here for a full explanation:

  • https://developer.apple.com/forums/thread/98071
  • https://www.cocoanetics.com/2017/02/itunes-connect-encryption-info/

Use TestFlight for internal testing

You can not deploy build with custom name for every release. Deploy builds should have same app name and bundle identifier should be same which is registered on apple developer account.if it is mismatched then user getting error while uploading app build on developer account.

For every build you should mention description of which feature or module is implemented and for which part testing build is release on TestFlight.



Related Topics



Leave a reply



Submit