OtaKit Channel Promotion and Rollback (Delivery)

OtaKit Channel Promotion and Rollback (Delivery)

1. 01

   Open the OtaKit dashboard and confirm the target app is selected in the app switcher

   Verify the app ID matches the client's capacitor.config.ts entry before touching any release, since a mismatched app ID sends the bundle to the wrong device fleet.

2. 02

   Upload the new web bundle through the OtaKit CLI

   Run the CLI upload against the client's build output. Delta compression means devices pull only changed files, so keep the bundle scoped to web assets rather than native binaries.

3. 03

   Release to the beta channel first

   Channel-based deploys let you stage on beta or a custom channel while production stays untouched. Watch the real-time dashboard for device pickup counts before promoting.

4. 04

   Set rollback thresholds on the release

   Automatic rollback triggers when a release fails health checks. Define the failure condition before promotion so a broken bundle reverts without a manual CLI intervention at 2am.

5. 05

   Promote the bundle to the production channel

   Promotion is a channel reassignment, not a re-upload, so the same delta payload already cached on beta devices carries over.

6. 06

   Monitor the dashboard for 24 hours post-promotion

   Track update adoption and error signals. If rollback fires, capture the failing release ID and the device cohort for the client incident note.

7. 07

   Log the release in the client retainer record

   Note the channel, bundle version, and rollback status. Agencies billing OTA delivery as a managed service need this trail to justify the monthly line item.