Create a patch
A patch updates Dart code for an already installed baseline release. Keep the baseline version, assets, native settings and signing unchanged.
Publish to the baseline
Section titled “Publish to the baseline”Replace the sample version with the actual registered release version. iOS commands run on macOS with baseline-compatible signing/export settings. Dart files, classes, functions and top-level variables can be added; native code/plugin native changes and bundled assets require a new release. Do not use allow-native-diffs or allow-asset-diffs to bypass these boundaries.
Activation and verification
Section titled “Activation and verification”The original installation checks and downloads automatically while online. A completed patch activates on a subsequent full process startup. It does not instantly replace the running app. Verify new behavior, repeat cold starts and interaction without reinstalling or clearing data; see the complete walkthrough. Patch size depends on the code change; no fixed size is promised.
Inspect and roll back
Section titled “Inspect and roll back”Use the console to select this app/release/patch and perform the normal rollback. Wait for the original updater to receive it and cold-start to verify baseline behavior returns. There is no patches disable or patches rollback CLI command. Do not mutate databases or delete device patch files.