Issue with - provide export compliance information

Hi All,


We are having issues with starting our internal testing of our app.

There is an exclamation mark next to the apps name in iTunes Connect and it says "Missing Compliance".

When we click "Provide export compliance information" we are provided with an option.

"Have you added or made changes to encryption features since your last submission of this app?"

To which we tick no and click "Start internal testing".

From this point we get an error message.


"Sorry, something went wrong. Try again later. If the problem persists."

We tried to contact support to no avail. Apples response was, we know about this.

If anyone has had similar issues please let me know how to solve them.


Thanks.

Same issue

Same Issue

Same issue

@charitiestrust - We were having this issue as well. After investigating the Networking console in Safari, it looks like a bug on Apple/ ITC's end:


<head>
<meta http-equiv=“Content-Type” content=“text/html;charset=ISO-8859-1"/>
<title>Error 409 </title>
</head>
<body>
<h2>HTTP ERROR: 409</h2>
<p>Problem accessing /v2/providers/314702/apps/350189835/builds/19985392/exportCompliance. Reason:
<pre>    ERROR-1: You must provide an answer for this question.</pre></p>
<hr /><i><small>Powered by Jetty://</small></i>
</body>
</html>


i.e. Looks like they just need to re-wire that No radio button up to the actual request to fix the issue. Pretty infuriating...we are going to add the key to the info.plist to sidestep the question.

Same issue.

still the same issue. when are they going to fix this?

we also have the same issue for the last 2 days.

Anywhere we can report this to apple?

I just realized that you can temporarily bypass this situation.



1) follow all procedures and submit your app to official review for app deployment

2) Once your app is in "ready to review state", your test flight is automatically turned from "missing compliance data" to "ready to submit"

3) Go into your test flight and submit it to review

4) go back to official submission and cancel the submission.



Hope apple fix this issue soon.

Same issue here.

An easier work around:

Instead of selecting

No
, select
Yes
.

Then select

Next
and another screen will prompt you asking if you use encryption. Select
No
here and then you should be able to select
Start Internal Testing

Hi All,

Just as a way of an update. This now seems to be fixed.

Although we are now having other issues with this similar thing. See other post.

Thanks,
Scott

Yes @amallard, your work around worked for me, while apple fix this issue.

Lael, this worked. Thanks.

This worked for me too.


Unbelievable how much takes it takes Apple to sort out this bugs.

Issue with - provide export compliance information
 
 
Q