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.

Up vote post of charitiestrust Down vote post of charitiestrust
14k views
Posted by
charitiestrust
Reply
Add a Comment

Replies

Same issue

Posted by
gdoudoussot
Up vote reply of gdoudoussot Down vote reply of gdoudoussot
Add a Comment

Same Issue

Posted by
Hanyz
Up vote reply of Hanyz Down vote reply of Hanyz
Add a Comment

Same issue

Posted by
chomi3
Up vote reply of chomi3 Down vote reply of chomi3
Add a Comment

@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.

Posted by
manderson123
Up vote reply of manderson123 Down vote reply of manderson123
Add a Comment

Same issue.

Posted by
zeromcmuffin
Up vote reply of zeromcmuffin Down vote reply of zeromcmuffin
Add a Comment

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

Posted by
ormediagroup
Post not yet marked as solved Up vote reply of ormediagroup Down vote reply of ormediagroup
Add a Comment

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

Posted by
larisuki
Up vote reply of larisuki Down vote reply of larisuki
Add a Comment

Anywhere we can report this to apple?

Posted by
ormediagroup
Up vote reply of ormediagroup Down vote reply of ormediagroup
Add a Comment

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.

Posted by
ormediagroup
Up vote reply of ormediagroup Down vote reply of ormediagroup
Add a Comment

Same issue here.

Posted by
iosdeveloper8897
Up vote reply of iosdeveloper8897 Down vote reply of iosdeveloper8897
Add a Comment

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
Posted by
amallard
Up vote reply of amallard Down vote reply of amallard
Add a Comment

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

Posted by
charitiestrust
Up vote reply of charitiestrust Down vote reply of charitiestrust
Add a Comment

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

Posted by
vishnu_mcube
Up vote reply of vishnu_mcube Down vote reply of vishnu_mcube
Add a Comment

Lael, this worked. Thanks.

Posted by
Part Time Monkey
Up vote reply of Part Time Monkey Down vote reply of Part Time Monkey
Add a Comment

This worked for me too.


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

Posted by
zirinisp
Up vote reply of zirinisp Down vote reply of zirinisp
Add a Comment