Rollbacks
Last updated
Was this helpful?
Last updated
Was this helpful?
This feature is limited to certain plans. Please visit our to learn more.
Rollbacks in Runway are special releases that use the build from a previous stable release, and, through an automated re-signing process, re-submit it as a new release version to quickly roll back problematic releases if needed.
Source version: the stable release version whose binary is reused for a rollback.
Target version: the release version being rolled back.
Rollback version: the release version of the rollback release.
Rollback releases in Runway are prepared by taking a previously released stable build (the source version) and running it though Runway’s re-signing process. This process updates the version string and build number (version name and version code on Android), re-signs the build with your signing key, and uploads it to the relevant store for re-submission as a new release version.
Rollback releases in Runway are a streamlined version of a typical Runway release – out of the box, they’re made up of only seven release steps:
Rollback build: details on the progress of the re-signing sequence and the source version upon which the rollback is based.
Screenshots & Metadata: a read-only view of the screenshots and metadata from the source version that will be used for the rollback.
Approvals: approval items that are relevant for rollbacks.
App store steps (submission, review, release)
The re-signing sequence is part of the Rollback build release step on rollbacks, and performs the following automations in this order:
Updates the build number & version string (version code and version name on Android) on the source version binary.
Once updated, re-signs the binary using your app's signing key.
Uploads the re-signed rollback build to the Play Console or App Store Connect.
The re-signing sequence will increment the build number / version code of the re-signed build as follows:
iOS: the latest build for the rollback version will be fetch from App Store Connect and incremented by one
Android: the highest version code on the production track will be fetched from the Play Console and incremented by one
On Android, rollback builds that display version name and version code anywhere in the app's UI will display the version name and version code of the source version.
Rollback releases do not automatically get cadence target dates applied. Runway will also override your default app store release settings – rollbacks will always start out with phased release disabled so they can be rolled out to everyone immediately. You can always change this setting on any given rollback release from Release settings > Edit release settings in the App Submission step prior to submission.
Many of the automations that Runway performs on during a normal release cycle aren’t relevant for rollback releases, or have special behavior that’s unique to rollbacks. The following automations will appear inactive for rollback releases:
Additionally, certain automations have special behavior for rollback releases. The following automations behave differently for rollback releases:
Android: the Submit app for review automation will appear inactive
[iOS only] If the Apply beta testing notes is enabled, Runway will apply a special set of rollback tester notes to the build in TestFlight.
[iOS only] If the Upload dSYMs to stability monitoring is enabled, Runway will upload the dSYMs generated during the re-signing process to your stability monitoring integration.
: Runway will automatically create an edit version (iOS) or track release (Android) immediately prior to rollback submission.
: Runway will select the latest successfully re-signed build in App Store Connect as part of the submission process.
: Runway will add the latest successfully re-signed build to the rollback production track release as part of the submission process.
: Runway will apply the source version's "What's new" or release notes to the rollback release as part of the submission process.
:
iOS: the Submit app for review automation will only be active if the Submit automatically when all release steps are ready option on the Prepare rollbacks automation is enabled. Rollbacks will be submitted for review if all previous steps are green as soon as the target release has gone live. See for more details.