Fix older versions
Many users stay on an older store version of your app for months. Over-the-air fixes normally reach only the newest version, because older versions have different native code and get their own bundles. So a bug you fixed today stays broken for everyone on 2.3, 2.2 and 2.1.
Healkite applies the same fix to every older version that's still in use.
How it works
- Open the release that contains the fix → What changed → the pull request → Fix older versions.
- Healkite lists the other app versions on the channel, with how many devices ran each in the last 30 days, for example 2.3 · 18,204 devices, 2.1 · 9,880 devices. Pick the ones to fix.
- For each one, your CI:
- checks out the commit the release on that version was built from,
- applies the change (
git cherry-pick -x, with-m 1for a merge commit), - builds, signs and publishes it to that app version as a guarded release, with the same steps and metrics as the release the fix came from,
- pushes a branch such as
healkite/backport-pr-381-to-2.3-…so the code is in your repository.
The release page shows each version's progress:
Fixed on 2.3 · Fixing 2.1 · 2.0 failed: the change doesn't apply cleanly (src/cart.ts)
From a terminal: npx healkite backport bpt_01j….
When it can't
- The code changed too much. If the change doesn't apply to that version's code, the job stops and says which files conflict. Fix that version by hand.
- The fix needs native code that version doesn't have (a new native module or permission). It builds, but the guarded rollout stops it once devices crash or roll back, and the bad bundle is never retried on those devices.
- No git source for that version. Releases published without the Healkite CLI from a git checkout don't record their commit, so there's nothing to build from. The dialog shows which versions those are.
Requirements
- Releases published with the Healkite CLI or GitHub Action from a git checkout (
fetch-depth: 0). - The Healkite workflow connected under Settings → CI.