iOS: an Xcode too old for the host macOS surfaces as 'Runner did not accept connection'
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 1-2 天
- 新手友好度
- 55/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- ios, typescript
调研方向
Read runner-error-classification.ts and runner-dev-tools-security.ts, then trace how runner startup failures are classified and whether retries are triggered. Reproduce with an Xcode version incompatible with the host macOS and inspect runner.log for the service hub failure. Done when this failure gets the proposed actionable reason and update hint without retrying.
由索引模型根据 Issue 内容生成。
描述
[!NOTE]
🤖 Opus 5.5 on behalf of Oliver
Summary
On a Mac whose Xcode is too old for its macOS, every iOS Simulator interaction (press, snapshot -i) fails with Runner did not accept connection or Daemon request timed out. The real cause is in runner.log, but the returned error doesn't mention it, so agents retry and then guess at the cause (SSH sessions, permissions).
Seen with macOS 27.2 (26B5101f), Xcode 26.6 (17F113), an iOS 26.5 simulator, and agent-device 0.21.23. open and screenshots kept working. Installing Xcode 27.0 fixed it without other changes.
What happens
runner.log repeats this for every xcodebuild test-without-building attempt, until ** BUILD INTERRUPTED **:
iOSSimulator: … unable to connect to "com.apple.instruments.deviceservice.lockdown"
(Error Domain=DVTiPhoneSimulatorErrorDomain Code=-1 "DTServiceHubClient failed to bless service hub for simulator <name> (<udid>)"
UserInfo={… NSUnderlyingError=… {Error Domain=DTServiceHubClient Code=1 "'localDeviceConnectionWithError:' failed but didn't provide an error."}})
The kernel log at the same moment shows why. macOS refuses to load Xcode's DTServiceHub:
AMFI: When validating /Applications/Xcode.app/Contents/SharedFrameworks/DVTInstrumentsFoundation.framework/Versions/A/Resources/DTServiceHub:
dynamic: com.apple.DTServiceHub disallowed without correct com.apple.private.amfi.version-restriction entitlement version
proc …: load code signature error 4 for file "DTServiceHub"
The same failure happened over SSH and inside the logged-in GUI session (DevToolsSecurity was disabled; I did not test it enabled). The CLI said the runner had already been restarted once during the request, and the retry failed the same way.
Repro
- Run a macOS release newer than the installed Xcode supports (here macOS 27.2 with Xcode 26.6).
agent-device open com.apple.Preferences --platform ios --udid <sim>agent-device press 200 300 --platform ios --udid <sim>→Runner did not accept connectionorDaemon request timed out. Watchinglog stream --predicate 'eventMessage CONTAINS "DTServiceHub"'during the press shows the AMFI lines above.
Proposal
Would you take a change that recognizes this as its own runner startup failure? Something like failed to bless service hub in runner.log → reason "Xcode cannot start its simulator service on this macOS", hint "Update Xcode to a version that supports this macOS", without retrying. runner-error-classification.ts and runner-dev-tools-security.ts look like the natural home.
A cheaper preflight is possible too, if you'd rather fail fast: macOS kills DTServiceHub --help with SIGKILL at launch in this state, while a working Xcode exits it normally with status 1. That ties agent-device to Xcode's internal file layout, though, so classifying the log seems safer.
Context: T3 Code installs agent-device on remote Mac hosts for its agents, which is where we hit this. We're happy to send a PR if this direction works for you.
- 主要语言
- TypeScript
- 星标
- 5k
- 派生
- 334
- 平均合并
- 13 小时 19 分钟
- 30 天内合并 PR
- 630
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
callstack/agent-device 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
callstack/agent-device#3627 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 88/100
callstack/agent-device#3353 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
callstack/agent-device#1869 ·
维护者通常 1 天内回复
-
iOS 26: `_UIFloatingBarContainerView` marks sheet content (and sometimes whole screens) as covered未关闭
难度 4/5 3-5 天 新手友好度 35/100
callstack/agent-device#3628 ·
维护者通常 1 天内回复
-
on-hold refactor
难度 2/5 1-3 小时 新手友好度 40/100
callstack/agent-device#3607 ·
维护者通常 1 天内回复
查看 callstack/agent-device 的全部 Issue
相似的 Issue
-
fix(frontend): correct VITE_IS_DEVELPOMENT typo in shared/app.ts and align dev environment flags未关闭
难度 2/5 1-3 小时 新手友好度 75/100
vicharanashala/ajrasakha#1439 ·
维护者通常 1 天内回复
-
approved check:passed streams:add
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
backnotprop/plannotator#1932 ·
维护者通常 1 天内回复
-
难度 2/5 半天 新手友好度 62/100
ibm-granite/granite.build#504 ·
维护者通常 2 天内回复
-
reproduced
难度 2/5 1-3 小时 新手友好度 82/100
anomalyco/opencode#55676 · 1 条评论 ·
维护者通常 1 天内回复