We have an application where there is a high frequency of build cycles. We wish to run automated tests where the “Sandbox user” will be able to load the next version of the app (from Test Flight?) and iterate the tests. We’re at the point where we can test this “one version” at a time, so we have Apple Pay Sandbox configurations working at least one build cycle at a time. Where we are now is the following process: Build the app, push to App Store Connect, make app available via test flight to the developer account members One member pulls the build to their iOS device via test flight same user logs out of their Apple ID on their iOS device, logs back in using the SANDBOX TEST user account Sandbox user on same iOS device now loads the test cards in the wallet Sandbox user launches app, tests application device user now logs out of the device from their Sandbox user account, logs back into the device with their Apple ID Developer account. on next build, go back to step 1 What we would like to see is: Take an iOS Test Device, log into the device with the SANDBOX USER account, loads Test cards to wallet TestFlight notifies user of new build, SANDBOX USER loads new build Sandbox user runs tests Sandbox user waits for next build. Are we doing the right thing? Is anyone else doing this? Comments please Thanks