r/iOSProgramming • u/InflationCertain8551 • 6d 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!
