|
2 | 2 |
|
3 | 3 | ## Unreleased |
4 | 4 |
|
| 5 | +- Changed (android): the snapshot helper release manifest no longer carries `installArgs`, and the |
| 6 | + helper installs with a fixed `adb install -r` like the IME helper. The array only ever spelled |
| 7 | + `install -r` plus the `-t` that #2603 retired with the `testOnly` flag, so the manifest → flag → |
| 8 | + option → flag round trip and its allowlist carried nothing. Older manifests that still contain |
| 9 | + the field parse unchanged; the field is ignored. The adb provider `install` capability now takes |
| 10 | + only `replace` (#2364). |
5 | 11 | - Fixed: BrowserStack sessions honour `--provider-project`, `--provider-build`, and |
6 | 12 | `--provider-session-name`. The capability builder emitted the legacy JSON Wire keys `device`, |
7 | 13 | `os_version`, and `app` at the top level next to the W3C `bstack:options` block; the hub treats a |
|
14 | 20 | BrowserStack runs for the session, as `bstack:options.appiumVersion`. Unset, BrowserStack falls |
15 | 21 | back to Appium 1.x, which predates the `mobile:` commands the interactor issues (`deepLink`, |
16 | 22 | `pressButton`, `activateApp`). |
| 23 | +- Changed (iOS runner): what recovers a stuck runner is decided by the recorded error, not by its |
| 24 | + wording. A readiness preflight marks the error it gives up with, and that marker is now the whole |
| 25 | + test for restarting the session and replaying the command — except for a request that was canceled, |
| 26 | + which that same catch also marks: a command nobody is going to send again has no restart to spend, |
| 27 | + and the session it would tear down may be one that still works. Two message checks decided it before, |
| 28 | + and a preflight reaches the caller in whatever shape its connect loop ended with — "Runner did not |
| 29 | + accept connection", "Runner endpoint probe failed", a killed `simctl` fallback, a post that ran out |
| 30 | + of its budget — so only some of those restarted and the rest failed the command. The other half is |
| 31 | + what no longer happens: when a slow |
| 32 | + boot spends the whole prepare budget, the health check reports "prepare ios-runner timed out", and |
| 33 | + that no longer wipes a restored `xcodebuild` artifact on the way to a rebuild — the runner session |
| 34 | + is invalidated and prepare retries with the artifact intact. Only a failure that indicts the |
| 35 | + artifact rebuilds it, so a runner that refuses the connection or never answers on any route still |
| 36 | + wipes it and rebuilds, which is what that rule is for. |
| 37 | + |
17 | 38 | - Changed (sessions): the implicit session is now keyed by workspace **and platform**, so one checkout |
18 | 39 | can drive iOS and Android without inventing a `--session` name for every command (#2580). An |
19 | 40 | implicit session was addressed by `cwd:<workspace>:default`, one slot per checkout, and it stayed |
|
0 commit comments