TestFlight - I Can't Submit to Beta, Nor Edit Test Info, Add External Users, Properly Complete Export Compliance

Question

Created Aug ’22

Replies 6

Boosts 2

Views 1.7k

Participants 3

Please help! I'm trying to replace an expired TestFlight Beta build and TestFlight seems to be only partially working for me at appstoreconnect.apple.com. I've tried Chrome and Safari.

Since last evening, I haven't been able to submit my latest builds to TestFlight Beta.

I uploaded two builds using Xcode Version 13.2.1 (13C100).

The following are some examples of what I've been seeing during the two attempts over the past 24 hours.

I caught a 500 in the logs, which may or may not be related. When that 500 occurred, App Store Connect wasn't even listing my app:

Both builds have completed processing. But when I view either of the latest 2 builds in TestFlight, I cannot edit the "What To Test" field. There is a hyphen in the textarea and I see no way to edit it:

testlfight-cant-edit-test-details-export-compliance.png

For a build I uploaded yesterday, I managed to update Export Compliance by adding "App Store Connect Users" group which triggered the Export Compliance prompt. But, after adding the internal group, I can't add an external groups to submit to Beta:

I made another internal "Test Group" and now it is the only other group available to add:

Thanks in advance for any help with this!

Boost

Answer 1

therobw OP

Aug ’22

Just a follow up. I walked my boss through the process of submitting to TestFlight Beta with their "Account Holder" account and everything worked fine without issue for them.

I've been using TestFlight since before it was cool, since before Apple's 2014 acquisition of the service. So the fact that I'm totally blocked for what should be my 40th or 50th Beta release seems very weird.

Therefore, the issue I'm experiencing seems to be related to either:

Just my account on our team,
or the "App Manager" et al permissions level in general perhaps (maybe I'm missing an announcement about a recent(?) change),
or the TestFlight backend is experiencing problems?

Regarding that last point about the stability of the backend, Apple's Status Page showed green checkmarks all the way down at the time. Apple is usually pretty good. AWS, on the other hand, has set the bar for how untrustworthy a status page can be.

But I definitely have more faith in Apple than AWS so I went ahead and walked my boss through the TestFlight Beta release process. While we did this walkthrough, I periodically reloaded the TestFlight portal on my side and noted that I was still seeing a seemingly broken UI.

0

Answer 2

ivendeng OP

Aug ’22

We also encountered this problem, which slowed down our testing schedule so much that testing was halted. All TestFlight links point to the online version, and we could not make any changes to the test group.

0

Answer 3

ivendeng OP

Aug ’22

I have two requests here that seem to be cancelled, not sure if this is normal.

0

Answer 4

ivendeng OP

Aug ’22

I can currently control TestFlight through the Connect app, but the web version still doesn't work.

0

Answer 5

therobw OP

Aug ’22

The issue appears to be resolved.

The following may just be a coincidence, but I'll describe what I did before it started working.

I have two developer accounts on my employer's team account. One account for my company email and one for my personal email Apple ID.

Again, might just be a coincidence, but I tried signing out of my company email account and signing into App Store Connect->TestFlight with my personal Apple ID. At which point, I had access to update the test information and add external testers!

I then signed out of my personal account and signed back into App Store Connect with my default company email account. And I had access to update the test info and add external tester groups as well.

Before I tried all this signing in-out stuff, I had already confirmed this morning that I was still seeing the issue. Either Apple fixed this issue later today or [queue magical thinking now:] I was hitting some sort of caching/cookies conflict or something?

So if you're still seeing this issue and you have two+ accounts on the same team, you may want to try logging out of one and logging back in with the other, assuming they have comparable user levels.

0

Answer 6

apson OP

Aug ’22

We still have no access to "External Testing" on a new app and can't seem to figure out why.

0