iOS physical device over Wi‑Fi: every tap fails with "lost its transport response" while snapshots work (USB works)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- ios, node.js, typescript
- 领域
- mobile-dev
调研方向
Start by tracing how press and click reach the iOS runner listener, then compare the Wi‑Fi connection failure in the runner logs with the successful USB case. The issue names no source files or tests, so locate the relevant transport entry points before making changes. Done means taps work over Wi‑Fi, or the CLI clearly reports that Wi‑Fi input is unsupported.
由索引模型根据 Issue 内容生成。
描述
Summary
On a Wi‑Fi‑paired physical iPhone, every press / click fails with Runner command "tap" lost its transport response, while open and snapshot -i work. The same device, app and env over a USB cable taps successfully on the first try.
Environment
- agent-device 0.21.35 (global npm), Node 22
- macOS 27, Xcode 27.0
- iPhone 18 Pro Max, iOS 27.0.1, Developer Mode on; Mac
DevToolsSecurityenabled - Runner signed with automatic signing via
AGENT_DEVICE_IOS_TEAM_ID/AGENT_DEVICE_IOS_BUNDLE_ID - Device paired over Wi‑Fi (CoreDevice), unlocked
Steps
agent-device open <bundle-id> --platform ios --udid <udid> --foreground→ healthy 33‑node snapshot- Any of:
press @e33 --settle,click 'label="You"' --settle,press 377 891
Actual
Error (COMMAND_FAILED): Runner command "tap" lost its transport response and the status probe failed, so agent-device invalidated the runner session instead of replaying the command.
On retry after the restart: iOS runner was already restarted during this request and "tap" still failed…. 4/4 attempts failed; snapshots between attempts keep succeeding.
The runner log never shows the tap command starting. The runner's listener rejects the incoming connection:
nw_path_evaluator_create_flow_inner NECP_CLIENT_ACTION_ADD_FLOW <uuid> [17: File exists]
nw_endpoint_flow_setup_channel [C3 fe80::<redacted>%en0.<port> initial channel-flow (satisfied (Path is satisfied), viable, interface: en0[802.11], …)] failed to request add nexus flow
nw_connection_create_from_protocol_on_nw_queue [C3] Failed to create connection from listener
On the next runner start: tcp_output [C3:1] flags=[R.] … state=CLOSED.
Expected
Taps work over Wi‑Fi like snapshots do, or agent-device reports that the Wi‑Fi transport is unsupported for input.
Isolation
- Connecting the same iPhone by USB (no other changes) →
press @e33 --settlesucceeds immediately (AGENT_DEVICE_RUNNER_COMMAND_COMPLETED command=tap ok=1). - A second agent-device daemon (0.21.31, embedded in another app) was running during both the Wi‑Fi failures and the USB success, so it does not appear to be the cause.
Side note
find <selector> performed a tap on the match, which surprised me — if that's intended, it might be worth calling out in help find.
- 主要语言
- TypeScript
- 星标
- 5.2k
- 派生
- 359
- 平均合并
- 13 小时 32 分钟
- 30 天内合并 PR
- 671
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
callstack/agent-device 的其他 Issue
-
bug ready-for-agent
难度 2/5 1-3 小时 新手友好度 77/100
callstack/agent-device#4018 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
callstack/agent-device#1869 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 43/100
callstack/agent-device#4110 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 57/100
callstack/agent-device#4109 ·
维护者通常 1 天内回复
-
needs-triage
难度 5/5 一周以上 新手友好度 25/100
callstack/agent-device#4106 · 1 条评论 ·
维护者通常 1 天内回复
查看 callstack/agent-device 的全部 Issue
相似的 Issue
-
area:cli bug P4
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
bug from-studio
难度 2/5 1-3 小时 新手友好度 65/100
esengine/DeepSeek-Reasonix#14868 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
linxiv-dev/linXiv#384 · 1 条评论 ·
维护者通常 1 天内回复
-
scope:core type:security
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
mailgun/mailgun.js#544 ·