[BUG] iOS Simulator panel/tool ignores iPhone Duo fold state and orientation (sideways view, stale 466x678 coords, screenshot captureFailed)
Status Open
Reported on v2.1.282
Maintainer reply None cached
Workaround ✓ Mentioned in description ↑
Activity 1 comment · opened Sep 25, 2026
Summary
In the Claude desktop app (Code tab), the iOS Simulator panel and the mcp__Claude_Code_iOS_Simulator__control tool don't follow the iPhone Duo (foldable) simulator's fold state or orientation. After the device is unfolded and put in landscape in Device Hub, the panel still shows the picture rotated 90° (sideways), the tool keeps reporting the folded screen's coordinate space, and screenshot fails.
Environment
- Claude desktop app 2.7032.0, Claude Code 2.1.282
- macOS 27.2 (26B5086k), Apple silicon
- Xcode 27.1 beta Device Hub (the iPhone Duo simulator runtime needs 27.1; Xcode 27.0 was also installed and running its own Device Hub)
- Simulator: iPhone Duo, iOS 27.1
Steps to reproduce
- Boot the iPhone Duo (iOS 27.1) simulator and open it in the Xcode 27.1 Device Hub.
- In Device Hub, press Open (unfolded) and use landscape.
- In the Claude Code tab, call the simulator tool with
action: "attach"for that device, thenaction: "screenshot". - Look at the Claude simulator panel.
Expected
- The panel shows the device the way Device Hub does: unfolded, landscape, upright.
attachreports the unfolded landscape coordinate space.screenshotreturns the current screen.
Actual
- The panel shows the app rotated 90° (sideways) compared with Device Hub.
attachstill reportsCoordinate space for tap/swipe: 466x678 points, the folded screen's size, after unfolding.screenshotfails withscreenshot failed: captureFailed.inspectreturns'inspect' is not available right now.xcrun simctl io <udid> screenshotworks and returns the correct upright unfolded-landscape image (2853×2007 px).- Workaround: drive the device through Device Hub, and capture with
simctl io.
Possibly related: #95466 (tap injection after the Xcode 27 / Device Hub switch).
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗