With App Ready To Launch, Appstoreconnect Refuses Version For TestFlight

I submitted our app in very close to release state, to ensure that there are no hidden problems that will trip us up, once we are ready to pull the trigger. So now I have an approved version, ready to launch.

We want to try to squeeze a couple more fixes and features in before launching, so today, I tried to upload a new version, with a minor change. It has a version number (1) the same as the ready to release app, and a build number ahead of it. (3.97 vs 3.96)

But I get an error saying the the new uploaded version must be ahead of the existing one, which it is. What is this about?

And in general, why is Apple so one-mindedly telling the world's funniest metajoke about a system designed to ensure the QA of products, which is a shambolic mess, not up to Microsoft standards in 2003? I'm not even going to get into the business of how it choked for two days on 4 screen shot uploads…

With App Ready To Launch, Appstoreconnect Refuses Version For TestFlight
 
 
Q