How to add new iOS devices to ensure test build delivery
SimplyE for iOS has CI that delivers builds to Firebase and TestFlight. Access to Firebase builds is controlled by a list of allowed devices that is defined on the Apple developer portal. We use Firebase for incremental development builds: the typical use case is to verify a ticket that has been fixed. Firebase is the better system to deliver builds to the same people, usually QA engineers.
When we start the process for a new release our CI system sends the build to TestFlight as well. TestFlight is better for QA'ing Release Candidates because it allows us to submit the same build to Apple for review and then wide distribution to users.
This video shows how to access the Apple developer portal and add the UDID of the device you want to enable to the SimplyE and Open eBooks ad-hoc provisioning profiles that are used by Firebase.
Then trigger a new run on the SimplyE Build workflow. Choose one of the following branches depending which build you're interested on:
- choose a
release/**branch if you want to update the last release candidate build; - choose the
developbranch if you're interested in updating the last incremental QA build; - choose a
feature/**branch for features currently under development.
When the workflow complete the new build should appear on Firebase. At this point if the build was never sent out, one will need to do so manually, inviting the new user to Firebase, or adding the tester to the build.