I’ve successfully gotten it to progress between these two states twice now, but I don’t know if it’s something I clicked on or if you just have to wait.
I think one part of the puzzle is you have to open up the build and input some testing notes. This enables a “Save” button. But there’s no “Submit to Review” button anywhere that I can find.
Actually you have to create the version first.. It has nothing to do with Test Flight sending the app for review are two distinct things.
To do what you have to do (If I understood your question well and your purpose is to send the app for review), you must open app store connect, select your app from the menu and click distribution at the top.
On the left, click on add version and start filling in all the fields that Apple requires, such as the description of the screens, the price, the availability…
At some point, it will ask you which build you want to use for the review and you will select it from a separate menu.
Ok, what I’m trying to do is specific to TestFlight.
Right now my app in TestFlight is in status Ready to Submit. When it’s in that status, you can’t add testers, which means you can’t get the app to test users through TestFlight.
In the past, somehow it did go to the next step, and then Apple ran an automated review and it was finally approved (in TestFlight) and able to go out to testers.
In theory you don’t have to press or do anything. When you submit a new build, Apple doesn’t check that version. After the end of the processing, and after choosing the users the app is automatically available for that group of users on TestFlight. They also receive an email..
I’ve been waiting all day and it hasn’t changed. “Ready to Submit” sure does imply that I need to do something (namely, Submit).
In my frenzy of exploratory clicking yesterday it somehow got submitted, which is how I deployed version 0.2.0 of my app. But version 0.3.0 is stuck and not progressing.
Can you share some screens? I would like to help you but I want to understand more.. I advise you to send a new build and wait for it to appear available..
You have to create a new external testing group. Even though you have the internal ones already, and they’ll get added automatically, they won’t work. You have to make a new external one, that is the only way to add the new build to it.
