The second time this recurred, I uploaded a build at 8:30 PM at night. At 1:30 in the morning, I received an email that it was ready to test. Great! When I went into my account, though, the build (123) and all other builds were marked expired. When I uploaded 124, it processed OK but then threw the beta contract error when I tried to attach it to the beta. My developer imagination here is wondering if there was a false positive on some security scan somewhere. As in, I sent him an email at 1:30 AM but he didn't act on it. People are sleeping! Abort! Better to have a human being review things than to take a chance on having an app go out to even a test group while people are sleeping. I'm very glad that layers of security are in place for our users. I just wish someone would tell me what the secret sauce is. Upload a build in the morning, wait 5 hours, install a test build immediately upon approval, what? The 422 is just so opaque, I can't iterate like this and it's holding my project back.

A Senior Advisor from developer support replied, reset things, asked me to try again in 48 hours, and I was able to upload another build. However, the problem has again recurred, with my build #124.