Repository navigation
chore(mobile): bump agent-device to 0.21.37 - #1735
Merged
okwasniewski merged 3 commits intoNov 13, 2026
Merged
Conversation
Contributor
There was a problem hiding this comment.
No issues found across 10 files
Heads up: you’ve reached your flex budget. Increase your flex budget or wait for usage to reset.
View guided diff | Re-trigger cubic
Contributor
There was a problem hiding this comment.
0 issues found across 3 files (changes from recent commits).
Heads up: you’ve reached your flex budget. Increase your flex budget or wait for usage to reset.
View guided diff | Re-trigger cubic
This was referenced Nov 13, 2026
This was referenced Nov 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates
agent-devicefrom 0.21.36 to 0.21.37 in@e2e-dev/mobile,@e2e-dev/e2b,@e2e-dev/limrun, and@e2e-dev/testmu(@agent-device/testmu). 0.21.37 ships the upstream fix for #1528 (callstack/agent-device#4210).unavailableis now listedbooted: false. The existingbooted === truefilter inpackages/mobile/src/pool.ts:169therefore leaves it out of the auto-selected pool, with no engine code change.device: adevicethat names such a phone now fails atbootinprepare("iOS device is not ready for automation"), before any test runs.postGestureStabilization: false, so the opt-out from the pendingmobile-skip-post-gesture-stabilizationchangeset now takes effect. I removed that changeset's sentence saying 0.21.36 ignores it.engine.test.tsadds the unreachable phone to the pool inventory as 0.21.37 lists it. It pins the engine's side of the contract; the fix itself is upstream.agent-device mcp, its AI SDK tools, orbatchsteps.Issue
Fixes #1528
Verified
Ran it locally: yes, on an iOS 26 simulator. A physical iPhone was paired but reachable over Wi-Fi.
SwiftUI example, deterministic suite: built packages, simulator UDID in
device,e2e run. 3/3 pass on 0.21.37:iOS
back(a left-edge swipe in 0.21.37, fix(ios): make back the verified left-edge swipe callstack/agent-device#4460): each version on Settings (agent-device back --json). Same outcome on both, so no docs change:COMMAND_FAILED, no reason, hint "Retry with --debug"COMMAND_FAILED,reason: back_swipe_no_change, hint "Press the visible back or close control by its ref from a fresh snapshot."Not verified live:
connectedduring the run, so both versions listed it booted. The upstream repro is in mobile: the auto-selected iOS pool includes a paired iPhone that is not connected #1528's comments.packages/mobile/tests/fixtures/snapshots/). I did not re-capture them: the mobile benchmark app is not built on this machine. 0.21.37 changes Android alert text and iOS 27 toolbars in snapshots (#4493, #4494 upstream). The mobile benchmark's committed recordings and the goldens may need a refresh if CI shows a tree diff.