Skip to main content

Managing the release process

Once you added a new release to a connected app and successfully configured it, you can go through the different release stages of the release process. You can only move to the next release stage after completing the current one, but you can return to a previous stage any time.

If you make changes to a previous stage, you must start the process over from that stage.

iOS

Android

  1. Release candidate: In the Release candidate stage, specify the release branch and select the Workflow that generates an IPA file.

    Env Vars from Release Management

    Release Management passes over certain Environment Variables to pipelines and workflows triggered by a release automation: Table 4, “Environment Variables passed to the builds from Release Management”.

  2. TestFlight: Upload the release candidate to TestFlight, and distribute it for testing.

  3. Approvals: You can create tasks for any stakeholder or team member whose approval is needed to continue with the release to the App Store.

  4. App Store review: Submit your update to review in the App Store, and get information on the approval progress.

  5. Release on the App Store: You can release your app to all users at the same time, or configure a phased release.

  1. Release candidate: In the Release candidate stage, specify the release branch and select the Workflow that generates an AAB file.

  2. Google Play upload and testing: Upload the release candidate to Google Play, and distribute it for testing.

  3. Approvals: You can create tasks for any stakeholder or team member whose approval is needed to continue with the release to Google Play.

  4. Release on Google Play: You can release your app to all users at the same time, or configure a staged rollout.

In this section: