@radhya/mach 2.0.39 → 2.0.41
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +4 -2
- package/dist/index.js +165 -165
- package/expo-plugin/index.js +5 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -78,7 +78,7 @@ Useful options:
|
|
|
78
78
|
| --------------------------- | ------------------------------------------------------------- |
|
|
79
79
|
| `--maestro` | Queue tests automatically after a successful `mach build` |
|
|
80
80
|
| `--maestro-flows <path>` | Flow file or directory, defaults to `.maestro` |
|
|
81
|
-
| `--maestro-device <name>` |
|
|
81
|
+
| `--maestro-device <name>` | iOS simulator model or identifier; iOS defaults to iPhone 17 Pro. Managed Android currently uses Pixel 6 |
|
|
82
82
|
| `--maestro-retries <n>` | Retry count for failed runs, from 0 to 10 |
|
|
83
83
|
| `--maestro-record` | Enable recording when supported by the runner |
|
|
84
84
|
| `--maestro-use-build-source` | Use flows from the build source snapshot instead of local upload |
|
|
@@ -145,7 +145,9 @@ mach ota rollback --update-id <updateId>
|
|
|
145
145
|
mach ota promote --update-id <updateId>
|
|
146
146
|
```
|
|
147
147
|
|
|
148
|
-
For Expo apps, `mach ota setup` writes `ota` config and wires `@radhya/mach/expo-plugin`. The plugin configures Expo Updates from `mach.config.json`, so updates are served from Mach instead of EAS Update. Install `expo-updates
|
|
148
|
+
For Expo apps, `mach ota setup` writes `ota` config and wires `@radhya/mach/expo-plugin`. The plugin configures Expo Updates from `mach.config.json`, so updates are served from Mach instead of EAS Update. Install `expo-updates`, then create and install one new native build after the initial setup. Previously installed binaries keep the update URL embedded when they were built and cannot be retrofitted by an OTA publish.
|
|
149
|
+
|
|
150
|
+
With the default `ON_LOAD` behavior, the first cold launch checks for and downloads a compatible update. The next cold launch runs it. Mach records unique downloaded, applied, and failed devices automatically from Expo Updates requests; app code does not call a metrics endpoint and never receives storage credentials.
|
|
149
151
|
|
|
150
152
|
Command flags always win over config values. For example, `mach ota publish --channel staging --runtime-version 1.2.0` overrides `ota.channel` and `ota.runtimeVersion`.
|
|
151
153
|
|