Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[Bug]: Keyboard toggle tools silently do nothing on Xcode 27 — System Events cannot attach to Device Hub

未关闭
#535 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
macos, typescript
领域
desktop, tooling

调研方向

Start by reading buildDeviceHubKeystrokeScript and _keyboard_shortcut.ts, then reproduce the reported osascript behavior with Device Hub visible. Trace the Device Hub branch alongside the Simulator.app window check and buildOpenSimulatorFrontendCommands. Done means the keyboard toggle tools use a supported interaction path or clearly report failure instead of returning success when the action has no effect.

由索引模型根据 Issue 内容生成。

描述

What happens

toggle_connect_hardware_keyboard and toggle_software_keyboard return success but change nothing on Xcode 27.

Both tools drive the simulator frontend through System Events. On Xcode 27 the frontend is Device Hub, and System Events cannot attach to it. The keystroke never arrives. osascript exits 0, so sendKeyboardShortcut reports success.

Root cause: Device Hub has no accessibility tree

Run these in the same shell, with Device Hub on screen showing a booted simulator:

$ osascript -e 'tell application "System Events" to return (count of attributes of application process "Device Hub")'
0

$ osascript -e 'tell application "System Events" to return (count of attributes of application process "Finder")'
20

Device Hub exposes zero accessibility attributes. Finder, as a control, exposes 20. UI elements enabled is true, so this is not a permissions problem.

Window and menu queries return nothing:

$ osascript -e 'tell application "System Events"
    set p to first application process whose bundle identifier is "com.apple.dt.Devices"
    return "windows: " & (count of windows of p) & ", menu bars: " & (count of menu bars of p)
  end tell'
windows: 0, menu bars: 0

That output is from a moment when Device Hub had a visible device window on screen. For the same process, background only is false and visible is true. lsappinfo reports !cgsConnection, bundle path=[ NULL ], Arch=!!none.

In buildDeviceHubKeystrokeScript, this means set frontmost of deviceHubProcess to true has no effect and the following keystroke goes nowhere.

The Device Hub branch does not detect the failure

The Simulator.app path checks for a window first:

if (focusResult.output.trim() === 'NO_WINDOW') {
  return {
    success: false,
    error: `No visible Simulator window found for "${device.name}". ...`,
  };
}

The Device Hub path has no equivalent check. It returns { success: true } whenever osascript exits 0.

The shortcut mapping is also stale

_keyboard_shortcut.ts sends the same shortcuts to both frontends:

const modifiers =
  shortcut === 'connect-hardware-keyboard' ? '{command down, shift down}' : '{command down}';

#346 describes these as Simulator.app bindings. Device Hub uses a different mapping under Device > Keyboard:

Menu item Shortcut
Keyboard Capture ⌘K
Simulate Hardware Keyboard none
Toggle Software Keyboard ⌥⌘K

⇧⌘K matches no item. ⌘K opens Keyboard Capture, not the software keyboard.

Fixing the mapping alone does not help, because the accessibility path is unavailable either way.

The menu works through synthetic mouse events

To confirm the menu item itself is functional, I drove it with CoreGraphics-level clicks instead of System Events:

  1. Opened Device > Keyboard. All three items rendered. Simulate Hardware Keyboard was checked.
  2. Clicked Simulate Hardware Keyboard. Reopened the menu. The checkmark was gone.
  3. Tapped a text field in the booted simulator and captured snapshot_ui.
Before toggle After toggle
82 elements, no keyboard 152 elements, including Q, W, shift, space, return

The menu item is reachable and effective. Only the accessibility route is blocked.

ConnectHardwareKeyboard is not a fallback

#346 lists defaults write com.apple.iphonesimulator ConnectHardwareKeyboard as an alternative. That domain belongs to Simulator.app, which Xcode 27 does not ship:

$ ls /Applications/Xcode.app/Contents/Applications/
Accessibility Inspector.app   Create ML.app       DeviceHub.app
FileMerge.app                 Icon Composer.app   Instruments.app

The key does not track the setting. With Simulate Hardware Keyboard checked, it read 0. After toggling the menu item, the key was absent from the domain.

com.apple.dt.Devices holds no keyboard key. No xcrun simctl subcommand exposes the setting; simctl ui covers only appearance, content_size, and increase_contrast.

Notes on reproducing

open_sim does not open a device window. Its schema is z.object({}), so no simulatorId reaches buildOpenSimulatorFrontendCommands and it runs open -a DeviceHub. open "devices:///manage/select?id=<UDID>" did not open one either.

What I did not test

I did not call the MCP tools directly, because simulator-management is not enabled in this project. I reproduced buildDeviceHubKeystrokeScript with osascript and observed no effect on either preference domain.

I cannot tell whether the missing accessibility tree is universal to Device Hub on Xcode 27 or specific to this machine.

Environment

  • XcodeBuildMCP 2.7.0
  • Xcode 27.0 (27A266a)
  • macOS 27.0
  • Frontend: Device Hub (com.apple.dt.Devices)
主要语言
TypeScript
星标
6.4k
派生
320
PR 合并指标
30 天内没有已合并 PR

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

getsentry/XcodeBuildMCP 的其他 Issue

查看 getsentry/XcodeBuildMCP 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。