TestFlight and App Store separated updates

Hello, I'm trying to understand the exportOptions file and how it can be used to control my releases. Seeing that an app has both the TestFlight and App Store sections I was under the impression that both App Store and TestFlight share the same builds, is that correct?

I'm trying to create two separate CI/CD processes to upload and automatically release exclusively to TestFlight only or App Store only. Given that the "app-store" method pushes a build to both, and there isn't a flag that can be passed to signify an automated release to TestFlight or an automated release to App Store, I'm not sure if there is something that I'm missing or if this is not possible to accomplish.

If builds are shared between the two, then I guess the better question is if there's a way to specify which build to release to which environment via cli?

Accepted Answer

Uploaded builds are shared by both App Store and Testflight, i.e. after you have successfully testflighted a build you can send the exact same build to app review.

I don't suggest trying to automate submitting builds to app review. You will want to manually review the app metadata etc. before pressing "submit" in the web interface.

"Uploaded builds" can be both selected for distribution to App Store Connect or Test Flight Only. The latter is not shared and can't be sent to app review. In Xcode Cloud you can create an archive for TestFlight only which will prevent these builds from accidently being sent to AppStore.

TestFlight and App Store separated updates
 
 
Q