Issue with - provide export compliance information

App Store Distribution & Marketing App Store Connect App Store Connect

charitiestrust OP

Created May ’17

Replies 36

Boosts 0

Views 14k

Participants 32

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.

Boost

makobec OP

Feb ’21

workaround doesn't work anymore.

Oleg Kasyan OP

Feb ’21

Works properly already

Sha1 OP

Feb ’21

It is working for me now [I think apple fixed it]

leonhardfromberlin OP

Feb ’21

wasn't working for me up until 30 minutes ago for version "2.1.9 (2)" of my app.
When i submitted the same version with an

increased build number as "2.1.9 (3)" and
having added "ITSAppUsesNonExemptEncryption" to the plist

suddenly version "2.1.9 (2)" was available for test (push notification on devices arrived) while "2.1.9 (3)" was still "processing" without possibility to enter encryption policy yes/no details. Weird.

gface250 OP

Feb ’21

Having the same issue with my latest build.

I have set the property as Exempt, It looked like it did not save properly (since build did not appear on testflight), so now each time i try to set it, it fails.

When i check the server response...its shows i am trying to edit an "already set" property (which shouldn't be possible).

{
"errors" : [ {
"status" : "409",
"code" : "ENTITY_ERROR.ATTRIBUTE.INVALID",
"title" : "The provided entity includes an attribute with an invalid value",
"detail" : "You cannot update when the value is already set.",
"source" : {
"pointer" : "/data/attributes/usesNonExemptEncryption"
}
} ]
}

jakusb OP

Feb ’21

Same issue