I got the same error when adding external testers in TestFlight for my new app (never been published). I logged a ticket on 15th October, and requested a call back this morning. Told the support engineer about the 422 error I saw in the browser dev tools. He said he had fixed an issue with my account, now to wait 48-hours then to submit a new build. I waited an hour, submitted a new build, same issue. I retried an hour later and it completed. Told him to check this forum!

I got the same error when adding external testers in TestFlight for my new app (never been published). I logged a ticket on 15th October, and requested a call back this morning. Told the support engineer about the 422 error I saw in the browser dev tools. He said he had fixed an issue with my account, now to wait 48-hours then to submit a new build. I waited an hour, submitted a new build, same issue. I retried an hour later and it completed. Told him to check this forum!

I got the same error when adding external testers in TestFlight for my new app (never been published). I logged a ticket on 15th October, and requested a call back this morning. Told the support engineer about the 422 error I saw in the browser dev tools. He said he had fixed an issue with my account, now to wait 48-hours then to submit a new build. I waited an hour, submitted a new build, same issue. I retried an hour later and it completed. Told him to check this forum!

I got the same error when adding external testers in TestFlight for my new app (never been published). I logged a ticket on 15th October, and requested a call back this morning. Told the support engineer about the 422 error I saw in the browser dev tools. He said he had fixed an issue with my account, now to wait 48-hours then to submit a new build. I waited an hour, submitted a new build, same issue. I retried an hour later and it completed. Told him to check this forum!