|
10 | 10 | (`apple_toolchain_probe_unavailable`) now fails once, not three times with a fresh startup budget |
11 | 11 | each time. A `retriable` failure from an external Apple runner provider is also no longer resent. |
12 | 12 | The error keeps `retriable: true`, so the caller's next request still tries again. (#2862) |
| 13 | +- Fixed (ios): a `fill` that replaces a field's text no longer types it faster than the app can keep |
| 14 | + up with. The synthesized replacement route posted characters at XCTest's default 60 characters per |
| 15 | + second, about 13 ms apart. A field whose app owns its value — a controlled React Native |
| 16 | + `TextInput`, a validator writing back — re-applies the value it observed a moment after the edit |
| 17 | + that produced it, and that write erases the characters the burst typed while it was in flight. The |
| 18 | + command reported ok, or later `TEXT_INPUT_COMMIT_NOT_OBSERVED`, on a value sitting stable short of |
| 19 | + the request: `ada@example` landing as `aexample`, first character and tail intact (#2080). |
| 20 | + Characters now arrive about 83 ms apart, an interval such a write lands inside before the next one |
| 21 | + arrives. A replacement is slower by ~70 ms per character and reaches roughly 500 characters inside |
| 22 | + the runner's 45 s budget (240 measured 21 s). An app that writes back later than one character |
| 23 | + interval can still corrupt a burst, and the verified element route most `fill` calls take is |
| 24 | + exposed to the same behaviour and tracked separately in #2903. (#2904) |
13 | 25 | - Fixed (mobile): a `get`, `is`, `find`, or `wait` selector read no longer answers from a tree that |
14 | 26 | a later command outdated. Selector reads reuse the session's stored tree for 750 ms after its |
15 | 27 | capture. Two cases outdated that tree without replacing it: a `wait text` satisfied by the |
|
0 commit comments