Selecting a release candidate
In the release candidate stage you can specify a release branch, and select a Workflow that can generate an .ipa or an .xcarchive file for iOS apps, or an .aab file for Android apps.
You can also choose to automatically upload a new release candidate each time you finish a build on the selected release branch with the specified Workflow.
To select a release candidate:
-
Open your release.
-
Select Release candidate on the left navigation bar.
-
Under the Configuration section, click on the button.
This will open up the Configure release candidate window.
-
Select a Release Branch and a Workflow using their respective dropdown menus.
Selecting a Workflow
Make sure that the Workflow you selected can generate either an
.ipaor an.xcarchivefile for iOS apps, or an.aabfile for Android apps and that it can deploy artifacts. The easiest way to ensure that is to add the following Steps to your Workflow:-
For iOS apps, the Xcode Archive & Export for iOS Step to generate the
.ipaor.xcarchivefile. -
For Android apps, the Android Build Step to generate the
.aabfile. -
Deploy to Bitrise.io - Apps, Logs, Artifacts Step to deploy artifacts. It must be of version 2.2.3 or higher.
-
-
If you want to upload all successful builds to TestFlight, click the radio button next to Upload all successful builds automatically.
-
Click .
-
If you opt to manually upload a selected build to use as the release candidate, you can do so by scrolling down to the Available builds section and toggling the Lock as RC next to the build. The selected build will be added to Active Build section.
If you don't use the toggle to lock a build as the release candidate, the latest build will be added to the Active Build section.
You can create additional tasks under the Checklists option.
When you have selected a release candidate and all tasks have been ticked off, Release candidate will be ticked off as well on the left navigation bar.