What Rollback Is

Rollback is how Bundle Drop moves users off a problematic OTA bundle and back to the previous working version.

This is not a separate "negative update" that you have to build and publish. It is a revert to the previously active bundle for that channel.

How Rollback Works

From the client point of view, rollback means:

• the current OTA bundle stops being the active target
• the app returns to the previous bundle it was on
• if there is no previous OTA bundle, the app falls back to the native bundle that shipped with the app binary

That means rollback can return users either to an older OTA bundle or all the way back to the native bundled version.

Where to Do It in the Dashboard

Rollback is handled from the dashboard on a channel's Bundles page.

The typical path is:

1. open your project
2. open the channel you want to manage
3. go to that channel's Bundles page
4. choose the bundle you want to roll back

Rollback is channel-scoped, so it affects that channel rather than every channel in the project.

When Teams Use It

Rollback is useful when:

• a release causes crashes or broken behavior
• you need to quickly return users to the last stable version
• you do not want to wait for a replacement OTA bundle to be prepared

What the Client Needs to Know

• rollback reverts users to the previous working bundle
• if the previous working version is the native bundle, the app falls back to that native bundle
• rollback does not require publishing a special reverse bundle

Related Docs

• For release tracks, see Channels.
• For gradual release control, see Staged Rollouts.
• For publishing bundles, see Uploading.