Test Flight "An error has occurred" - Export Compliance Information

Question

Created Feb ’21

Replies 61

Boosts 0

Views 16k

Participants 53

I am trying to submit an iOS build to internal testing on App Store Connect. The build is uploaded and processed properly. However, when answering the Export Compliance Information question I get "An error has occurred. Try again later.". I have been able to submit this app many times before today. I checked the network logs and the App Store is giving the following error:

Code Block {  "errors" : [ {
    "id" : "904dede1-5b87-4171-acf0-63d8430b0675",
    "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"
    }
  } ]
}

Is anyone else seeing this error today?

Answer 1

javiernanni OP

Mar ’21

To solve this issue:

Submit the build for review (not for Test Flight, but for final App Store release)
Test Flight status of the app will change from Missing compliance to Ready to submit
Developer Reject the build you just submitted for final review (unless you actually want it to be reviewed!)

That worked for me.

Answer 2

dshaffer OP

Mar ’21

Same issue here. Cmon Apple!

Answer 3

gp55 OP

Mar ’21

when they gonna fix this shiit.

Answer 4

ShubhamBathe OP

Mar ’21

Same here, any work around please post.

Answer 5

HollettGaming OP

Mar ’21

Same issue here for me too, I submitted a bug report

Answer 6

siliconAvatar OP

Mar ’21

Same issue here, this is quite humiliating and I don't know what to tell my customers except that Apple is broken. Please fix.

Answer 7

siliconAvatar OP

Mar ’21

Just curious, has anyone been successful at actually "Trying agian later" as the error suggests?

I need to add new beta testers, should I try again later or is Testflight completely grounded?? Please someone let me know!

Answer 8

gp55 OP

Mar ’21

if you submit in the morning at least for me in US, I haven't had any issue, if i do after 2/3 PM, i still get same error, i have to wait till next day morning.

Answer 9

LuisVenturo OP

Nov ’21

I was reviewing how to upload the beta versions of my application to TestFlight and I found that suffixes such as -beta1, -beta2 can be used, so, currently I had version 2.0.1 in production and I tried to upload 2.0.1-beta1 and this generated the error since I should have uploaded the beta of v2.0.2 and not v2.0.1 since the latter can no longer have betas because it is in production. So using 2.0.2-beta1 instead of 2.0.1-beta1 fixed the problem for me.

Answer 10

feqfeqqfeqfefeq OP

Nov ’23

2024, issue appears again

Answer 11

JacobPeacey OP

Feb ’24

Hi! I have just started experiencing this too. it's not just me, so have my team members. We can only assume it's something to do with the App Store Connect Servers, but it sure is annoying.