Flutter hotfix,
live in minutes.

The hotfix playbook

1. Fix the Dart code

Make the smallest change that fixes the bug, on the code of the release users have. Keep native code, plugins and assets as they are: those need a store release.

2. Publish it over the air

$ overpush patch android --rollout-percent 10
$ overpush patch ios --rollout-percent 10

OverPush finds the release you shipped, builds the patch against it and checks it. Ten percent of devices get it first.

3. Watch, then roll out to everyone

The dashboard shows installs and failures as phones report in. When it looks right, raise the rollout to 100%. Phones download the fix in the background and run it at the next launch.

4. If the fix is wrong, pull it back

Roll the patch back for everyone with one command, from the CLI or the dashboard. A patch that stops the app from starting is also removed on the phone by itself, even offline.

Before the first hotfix

Over-the-air fixes work for builds released with OverPush. Set it up once, before you need it:

$ curl -fsSL https://overpush.in/install.sh | bash
$ overpush login
$ overpush init
$ flutter pub add overpush
$ overpush release android
$ overpush release ios

Submit those builds to the stores as usual. From then on, every fix is one command. The getting started guide walks through it.

Hotfixes from CI

On Pro and up, a CI token lets GitHub Actions or Codemagic publish the patch when a hotfix branch is merged, so the fix goes out with the same review as any other change.

More

• Update a Flutter app without the App Store review
• Flutter OTA updates: what they can change and store rules
• Pricing: free for 5,000 update installs a month