r/iOSProgramming • • 4d ago

Question Can't submit a build for external TestFlight testing: always "There was an error processing your request. Please try again later." (422)

Has anyone else run into this? I've been stuck for several days and haven't heard back from Apple support yet.

The problem

Whenever I add an external group or an individual external tester to a build, App Store Connect shows:

There was an error processing your request. Please try again later.

The API (POST /v1/betaAppReviewSubmissions) returns the same thing:

422 ENTITY_UNPROCESSABLE

"There was an error processing your request." / "Please try again later."

Internal testing works fine, and the build installs through TestFlight without any issue.

Context

  • This is my third app on this developer account. The first two went through external TestFlight review with no problem, using the same process.

  • Free app, iOS 17+, no login, no network calls, no in-app purchases

  • Primary language is English (Canada)

  • The app references alcohol (cocktail recipes), so it's rated 17+

What I've checked (all confirmed through the API)

  • The build is processed (VALID), and its external state is READY_FOR_BETA_SUBMISSION

  • Export compliance is set (ITSAppUsesNonExemptEncryption = NO)

  • Test Information is complete in the primary locale (en-CA) and in en-US: beta description, feedback email, privacy policy URL, marketing URL

  • Beta App Review contact info is complete (phone in +1 format) and the review notes are filled in. No sign-in is required.

  • "What to Test" is filled in for the build

  • The beta license agreement has text

  • The age rating is complete, and the category, content rights and privacy policy URLs are set for every localization

  • The Free Apps agreement is Active

  • No beta review submission is pending, and the older builds are expired

  • I tried several builds, a new external group, individual testers, other browsers, and waiting a day

Since my other apps worked fine, the problem seems to be with this app rather than the account. Has anyone seen this before? If you fixed it, what was the cause, and did Apple support have to unblock it on their side?

Thanks!

2 Upvotes

16 comments sorted by

1

u/InflationCertain8551 2d ago

Tried everything below, nothing worked ! Still waiting for my email reply. I’ve decided to submit the app anyway, to see if I might get a more verbose error :)

1

u/Background_Pie_5682 4d ago

I haven't hit this exact 422 but a couple of things that have unstuck similar cases: re-open and re-save the age rating questionnaire, since Apple updated it and an old unsaved answer can silently block submissions. Also make sure the app version page itself is complete (privacy answers, category, a screenshot), because the external review pulls from that too. If none of that helps, a TestFlight-specific ticket through Contact Us gets picked up faster than the general ones in my experience.

1

u/InflationCertain8551 4d ago

Thx, I'll check that asap. I didn't know for the screenshot and I have none.

1

u/InflationCertain8551 2d ago

Didn't work, unfortunately

1

u/himmetagadev 4d ago

A useful next step is to give support one reproducible attempt with the build number, approximate submission time, and any request or correlation ID returned with the 422. Since several builds and a new external group fail in the same way, ask them to check the beta review submission state for that app on their side. That gives them a specific request to trace rather than only the generic error. It may also help to include the successful internal-testing result as a comparison.

1

u/InflationCertain8551 4d ago

Yup, I did email them. Still waiting for a reply after 1 week.

1

u/himmetagadev 3d ago

You could try requesting a phone call through Apple Developer Contact Us and mention the existing case number. It may also be worth checking that the Test Information and beta review details for the build are filled in, although that may not explain the 422 error.

2

u/InflationCertain8551 2d ago

Yes, it's next on my list :/

1

u/himmetagadev 4d ago

A week is a long wait when a submission is blocked. If you have a case number, a follow-up in the same thread may help keep the build details and 422 error together. Hope you hear back soon.

1

u/SutharatLofski_44 4d ago

try bumping the major or minor version number and uploading a fresh build, not just incrementing the build number. sometimes the backend gets stuck in a weird state on a specific version train and throws a generic 422 no matter what you do.

1

u/InflationCertain8551 2d ago

Didn't work !

1

u/Enlitened 4d ago

Since you're already hitting the API, dump the full JSON body of the 422 rather than just the title and detail. App Store Connect errors often carry more than the dashboard shows: each entry in "errors" can have a "source.pointer" naming the field it didn't like, and sometimes a "meta.associatedErrors" block listing the real reasons behind a generic message. The website throws all of that away and just shows "try again later".

If the body really is only the generic text, I'd also GET the build's betaBuildLocalizations and the app's betaAppLocalizations and check there's an entry for every locale the app has, not just en-CA and en-US. A missing one for a locale you added later is easy to miss in the UI.

If both come back clean it's probably stuck on Apple's side like the other comment says, and the request ID from the response headers is the thing to give support.

1

u/InflationCertain8551 2d ago

Yup, the JSON response is pretty generic

{
  "errors": [
    {
      "id": "219424a8-ca34-4b97-9ea4-084b704bc0e2",
      "status": "422",
      "code": "ENTITY_UNPROCESSABLE",
      "title": "There was an error processing your request.",
      "detail": "Please try again later."
    }
  ]
}

1

u/Needle_In_Red 3d ago

check the beta app review info has a contact email and phone filled in, thats easy to miss. otherwise its probly on apples end

1

u/InflationCertain8551 1d ago

Yup, all filled

1

u/AkhnafAban 20h ago

Hey, i have the same problem too, do you gave any update about this? i already contact the apple support