Changelog

What changed in the CLI and the app package. Update the CLI by running the installer again.

App package 1.2.13

One more try. A patch that fails at startup is tried once more before the device turns it off, so a one-off crash no longer removes a good patch. See Automatic rollback.
Android: only a real crash counts as a failure (Android 11 and later). The system closing the app, or the app closing itself, doesn't.
The dashboard counts a device as failed only while it is failing. Once the retry or a newer patch runs, it leaves the count. A patch that keeps failing on one device counts once.
Needs a new store build with overpush: ^1.2.13. Builds with an earlier package keep the earlier behaviour.

Now under the OverPush License, for use with the OverPush service. No code changes.
Android: works with Android Gradle Plugin 9's built-in Kotlin, and newer Flutter no longer warns that overpush applies the Kotlin Gradle Plugin. Apps on older Flutter build as before.
The app sends a report only when its patch changes (a download, a patch starting, a store update or an error), so opening the app often sends nothing.

iOS on Flutter 3.47. iOS releases and patches work on Flutter 3.47.5, 3.47.6, 3.47.7, 3.47.8 and 3.47.9, as well as 3.41.4; the CLI uses the right build tools for your project's Flutter version. Flutter 3.47 needs CLI 1.2.15 or later.
Clearer error messages. When iOS isn't available for your Flutter version yet, the message points to Flutter versions.
iOS commands no longer fail on a computer where Flutter has never been run before.
Every icon in every release. Releases keep all Material and Cupertino icons, so patches can use any of them. Set keep_all_icons: false for a smaller app; see Configuration. Releases already out keep what they were built with.
Windows: Android builds no longer fail with "this and base files have different roots" when the project and the pub cache are on different drives, or with a file "being used by another process" right after a release.