pod
Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for XcodeBuildMCP

Pod holds 24 of 304 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to XcodeBuildMCP.

Most discussed

[Bug]: Clean fails on my iOS only project

Bug Description

It looks like it's because I don't have a macOS target. Here's the output of the tool call

❌ [stderr] 2025-08-21 16:10:42.575 xcodebuild[8774:116510104]  DVTDeviceOperation: Encountered a build number "" that is incompatible with DVTBuildVersion.
❌ [stderr] 2025-08-21 16:10:42.577 xcodebuild[8774:116510070] [MT] DVTDeviceOperation: Encountered a build number "" that is incompatible with DVTBuildVersion.
❌ [stderr] 2025-08-21 16:10:42.709 xcodebuild[8774:116510070] Writi

[Read the thread](https://github.com/getsentry/XcodeBuildMCP/issues/99) · 2025-08-21 · closed · external user · 11 comments

### [Feature]: Identify how we can utilise the broader Model Context Protocol

### Feature Description

I would like to explore how we can support the broader Model Context Protocol specification in addition to our existing tool and sampling capabilities.

I'm interested in how resources, prompts and elicitation could be used to improve the DX for the agent as well as the end-user. 

## Useful resources:
https://modelcontextprotocol.io/llms-full.txt
https://modelcontextprotocol.io/introduction
https://github.com/modelcontextprotocol/typescript-sdk

### Use Cases

_No respo

[Read the thread](https://github.com/getsentry/XcodeBuildMCP/issues/78) · 2025-07-22 · closed · outside contributor · 14 comments

### [Feature]: Identify how we can utilise the broader Model Context Protocol

### Feature Description

I would like to explore how we can support the broader Model Context Protocol specification in addition to our existing tool and sampling capabilities.

I'm interested in how resources, prompts and elicitation could be used to improve the DX for the agent as well as the end-user. 

## Useful resources:
https://modelcontextprotocol.io/llms-full.txt
https://modelcontextprotocol.io/introduction
https://github.com/modelcontextprotocol/typescript-sdk

### Use Cases

_No respo

[Read the thread](https://github.com/getsentry/XcodeBuildMCP/issues/78) · 2025-07-22 · closed · outside contributor · 14 comments

### [Feature]: Filter build output for warnings and errors

### Feature Description

Often, when I use the tool `build_sim_id_ws` the context is blown away with a single invocation. I'm guessing this is because the build log output is filled with things like compiler commands that don't really matter to my LLM agent. It would be nice if these tools could have a flag that the agent could set that would filter all the cruft out and just present the LLM with warnings, errors, test failures, etc.

My agent often resorts to commands like this instead:

```bas

[Read the thread](https://github.com/getsentry/XcodeBuildMCP/issues/68) · 2025-06-11 · closed · outside contributor · 15 comments

### [Feature]: Filter build output for warnings and errors

### Feature Description

Often, when I use the tool `build_sim_id_ws` the context is blown away with a single invocation. I'm guessing this is because the build log output is filled with things like compiler commands that don't really matter to my LLM agent. It would be nice if these tools could have a flag that the agent could set that would filter all the cruft out and just present the LLM with warnings, errors, test failures, etc.

My agent often resorts to commands like this instead:

```bas

[Read the thread](https://github.com/getsentry/XcodeBuildMCP/issues/68) · 2025-06-11 · closed · outside contributor · 15 comments

### [Feature]: is it possible to run on the build on hardware devices like i can do it from xcode via wifi?

### Feature Description

is it possible to run the build via the llm chat on a hardware device that is connected to the wifi ? i love the  build command to run on the ios simulator via build_run_ios_sim_name_proj in the llm chat, is there a way to make it work for hardware devices, especially via wifi? I have to do this last step via xcode at the moment. I know there is the tool build_ios_device, but it doesn't seem to work for wifi, only usb.

### Use Cases

_No response_

### Example Interacti

[Read the thread](https://github.com/getsentry/XcodeBuildMCP/issues/54) · 2025-06-07 · closed · external user · 12 comments

### Seems to break Claude Code.

This MCP appears to work perfectly fine in Cursor for me, but as soon as I add it to Claude Code, every subsequent message fails with:

`⎿  API Error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"tools.46.custom.name: String should have at most 64 characters"}}`

Removing the MCP from my Claude config fixes the issue.

[Read the thread](https://github.com/getsentry/XcodeBuildMCP/issues/3) · 2025-04-21 · closed · outside contributor · 12 comments

### Seems to break Claude Code.

This MCP appears to work perfectly fine in Cursor for me, but as soon as I add it to Claude Code, every subsequent message fails with:

`⎿  API Error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"tools.46.custom.name: String should have at most 64 characters"}}`

Removing the MCP from my Claude config fixes the issue.

[Read the thread](https://github.com/getsentry/XcodeBuildMCP/issues/3) · 2025-04-21 · closed · outside contributor · 12 comments

## Most recent

### [Feature]: UI automation on physical devices via CoreDevice HID (pymobiledevice3)

### Summary

The `device` workflow can build, install, launch, stop and test on a physical device, but has no input or capture tools — `ui-automation` is simulator-only by design ("UI automation and accessibility testing tools for iOS simulators"). That leaves agent-driven verification on real hardware out of reach, even though the device itself exposes everything needed.

I'd like to propose adding device-scoped `tap` / `swipe` / `type` / `button` and `screenshot` to the `device` workflow, and 

[Read the thread](https://github.com/getsentry/XcodeBuildMCP/issues/519) · 2026-08-26 · open · external user · 0 comments

### [Feature]: UI automation on physical devices via CoreDevice HID (pymobiledevice3)

### Summary

The `device` workflow can build, install, launch, stop and test on a physical device, but has no input or capture tools — `ui-automation` is simulator-only by design ("UI automation and accessibility testing tools for iOS simulators"). That leaves agent-driven verification on real hardware out of reach, even though the device itself exposes everything needed.

I'd like to propose adding device-scoped `tap` / `swipe` / `type` / `button` and `screenshot` to the `device` workflow, and 

[Read the thread](https://github.com/getsentry/XcodeBuildMCP/issues/519) · 2026-08-26 · open · external user · 0 comments

### test_sim reports SUCCEEDED with 0 tests when per-call projectPath is ignored

## Summary

`test_sim` appears to ignore a per-call `projectPath` and use the session default instead. When the two differ, it reported `SUCCEEDED` having run **zero tests**.

## What happened

I had several agents working concurrently in separate git worktrees of one repo. Session defaults were set once, pointing `projectPath` at the main checkout:

session_set_defaults projectPath: /src/PinPoint.xcodeproj scheme: PinPoint simulatorName: iPhone 17 Pro


An agent working in `<

[Read the thread](https://github.com/getsentry/XcodeBuildMCP/issues/517) · 2026-08-23 · open · external user · 1 comment

### test_sim reports SUCCEEDED with 0 tests when per-call projectPath is ignored

## Summary

`test_sim` appears to ignore a per-call `projectPath` and use the session default instead. When the two differ, it reported `SUCCEEDED` having run **zero tests**.

## What happened

I had several agents working concurrently in separate git worktrees of one repo. Session defaults were set once, pointing `projectPath` at the main checkout:

session_set_defaults projectPath: /src/PinPoint.xcodeproj scheme: PinPoint simulatorName: iPhone 17 Pro


An agent working in `<

[Read the thread](https://github.com/getsentry/XcodeBuildMCP/issues/517) · 2026-08-23 · open · external user · 1 comment

### [Bug]: Simulator test fails on mixed iOS and watchOS test plans in 2.7.0

### Bug Description

`simulator test` fails on XcodeBuildMCP 2.7.0 when the scheme's test plan contains both iOS and watchOS unit test targets. The same command, project and simulator pass on 2.6.2.

2.7.0 builds the project and discovers both tests, then the prepared test phase fails to resolve the requested iOS Simulator. Removing only the watchOS test target from the test plan makes 2.7.0 pass.

I have attached a standalone repro with three targets and no dependencies, package manager or code

[Read the thread](https://github.com/getsentry/XcodeBuildMCP/issues/514) · 2026-08-11 · open · external user · 0 comments

### [Bug]: Simulator test fails on mixed iOS and watchOS test plans in 2.7.0

### Bug Description

`simulator test` fails on XcodeBuildMCP 2.7.0 when the scheme's test plan contains both iOS and watchOS unit test targets. The same command, project and simulator pass on 2.6.2.

2.7.0 builds the project and discovers both tests, then the prepared test phase fails to resolve the requested iOS Simulator. Removing only the watchOS test target from the test plan makes 2.7.0 pass.

I have attached a standalone repro with three targets and no dependencies, package manager or code

[Read the thread](https://github.com/getsentry/XcodeBuildMCP/issues/514) · 2026-08-11 · open · external user · 0 comments

### [Bug]: Device Hub opens for stable Xcode when Xcode 27 beta is co-installed

### Bug Description

When Xcode 26 stable and Xcode 27 beta are installed together, XcodeBuildMCP
2.7.0 opens the beta-only Device Hub even when `DEVELOPER_DIR` explicitly
selects stable Xcode and the target is an iOS 26.5 simulator.

This crosses the selected toolchain boundary. Stable Xcode 26 ships
`Simulator.app`; Device Hub is bundled only inside Xcode 27 beta on this host.

The cause appears to be the frontend candidate order in
[`focus-policy.ts`](https://github.com/getsentry/XcodeBuildMC

[Read the thread](https://github.com/getsentry/XcodeBuildMCP/issues/513) · 2026-08-11 · open · external user · 1 comment

### [Bug]: Device Hub opens for stable Xcode when Xcode 27 beta is co-installed

### Bug Description

When Xcode 26 stable and Xcode 27 beta are installed together, XcodeBuildMCP
2.7.0 opens the beta-only Device Hub even when `DEVELOPER_DIR` explicitly
selects stable Xcode and the target is an iOS 26.5 simulator.

This crosses the selected toolchain boundary. Stable Xcode 26 ships
`Simulator.app`; Device Hub is bundled only inside Xcode 27 beta on this host.

The cause appears to be the frontend candidate order in
[`focus-policy.ts`](https://github.com/getsentry/XcodeBuildMC

[Read the thread](https://github.com/getsentry/XcodeBuildMCP/issues/513) · 2026-08-11 · open · external user · 1 comment

### [Bug]: Simulator tools silently ignore explicit arguments when session defaults are set

### Bug Description

The simulator tools (`build_sim`, `build_run_sim`, `test_sim`) silently discard explicitly-passed arguments when session defaults are configured. The provided value is not merged, not warned about, and not echoed — the session default (or an empty value) is used instead.

This is easy to miss because the response's `request` object reports the *effective* values, so the discard is only visible if you compare it against what you sent.

Note this is distinct from #443: there t

[Read the thread](https://github.com/getsentry/XcodeBuildMCP/issues/509) · 2026-08-09 · open · external user · 0 comments

### [Bug]: Simulator tools silently ignore explicit arguments when session defaults are set

### Bug Description

The simulator tools (`build_sim`, `build_run_sim`, `test_sim`) silently discard explicitly-passed arguments when session defaults are configured. The provided value is not merged, not warned about, and not echoed — the session default (or an empty value) is used instead.

This is easy to miss because the response's `request` object reports the *effective* values, so the discard is only visible if you compare it against what you sent.

Note this is distinct from #443: there t

[Read the thread](https://github.com/getsentry/XcodeBuildMCP/issues/509) · 2026-08-09 · open · external user · 0 comments

### scaffold-ios: scheme references a test plan file that is never generated

## Summary

`scaffold-ios` generates a shared scheme whose `<TestPlans>` section references `container:<Name>.xctestplan`, but that file is never generated. Running tests fails with: `Tests cannot be run because the test plan "<Name>" could not be read.`

## Environment

- xcodebuildmcp 2.6.0
- Xcode 26.4 (Build 17E192)
- macOS 26.4.1

## Reproduction

1. Scaffold a project:

xcodebuildmcp project-scaffolding scaffold-ios --project-name SmokeTest --output-path /tmp/smoke --bundle-identifier c

Read the thread · 2026-08-02 · open · external user · 1 comment

scaffold-ios: missing XCLocalSwiftPackageReference makes first build fail (Missing package product)

Summary

scaffold-ios generates an Xcode project whose app target declares a dependency on the bundled local Swift package product (<Name>Feature), but the generated project.pbxproj contains no XCLocalSwiftPackageReference. The first build fails with Missing package product.

Environment

  • xcodebuildmcp 2.6.0 (brew, getsentry tap)
  • Xcode 26.4 (Build 17E192)
  • macOS 26.4.1

Reproduction

  1. Scaffold a project:
xcodebuildmcp project-scaffolding scaffold-ios --project-n

[Read the thread](https://github.com/getsentry/XcodeBuildMCP/issues/502) · 2026-08-02 · open · external user · 1 comment

### [Feature]: Support latest simulator runtime within an OS major version

### Feature Description

When a beta runtime for the next iOS major version is installed, XcodeBuildMCP cannot select the latest simulator runtime within the current major version.

For example, this machine has an available `iPhone 17 Pro` on iOS 26.5 and an available iOS 27.0 simulator for a different device type. The desired selection is “iPhone 17 Pro on the latest installed iOS 26 runtime.”

### Environment

- XcodeBuildMCP 2.7.0 (Homebrew)
- Xcode 26.6 (17F113)
- macOS 26.6

### Reproducti

[Read the thread](https://github.com/getsentry/XcodeBuildMCP/issues/498) · 2026-07-28 · open · external user · 1 comment

### Warden weekly sweep

## Warden Scheduled Scan Results

**Run:** 2026-08-24T06:29:09.646Z
**Commit:** `e6ef59b`

### Summary

| Severity | Count |
|----------|-------|
| High | 1 |
| Medium | 4 |
| Low | 3 |

### Findings

#### [`scripts/create-homebrew-formula.sh`](https://github.com/getsentry/XcodeBuildMCP/blob/e6ef59b49b44012c824f0a0de261c96142e37390/scripts/create-homebrew-formula.sh)

- `BR3-5ST` **Unsanitized CLI arguments enable Ruby code injection into generated Homebrew formula** ([L81-L90](https://github.co

[Read the thread](https://github.com/getsentry/XcodeBuildMCP/issues/495) · 2026-07-27 · open · external user · 0 comments

### [Feature]: Add set_sim_orientation for iOS Simulator automation

### Feature Description

XcodeBuildMCP exposes simulator-level controls such as appearance, location, status bar overrides, keyboard settings, and hardware buttons, but it cannot currently change device orientation.

Rotating a selected simulator currently requires interacting with Simulator.app. There is no public `simctl` rotation command. `UIWindowScene.requestGeometryUpdate` only requests an orientation change for the calling app, so it cannot rotate an arbitrary simulator or SpringBoard.

P

[Read the thread](https://github.com/getsentry/XcodeBuildMCP/issues/494) · 2026-07-26 · open · external user · 1 comment

### Build hangs forever at "Planning" — xcodebuild pipe deadlock on stdout write(), amplified by stale MCP server instances

## Summary

Local builds via XcodeBuildMCP (`build_sim` / `build_device` / `test_sim`, etc.) intermittently hang forever at the **"Planning"** phase and never reach compilation. The MCP tool call has **no self-timeout**, so the agent session wedges until the process is killed or the machine is restarted.

Root cause (stack-confirmed): **pipe deadlock** — `xcodebuild` blocks in `write()` on stdout while flooding destination-resolution warnings during planning. This is amplified by **stale / multi

[Read the thread](https://github.com/getsentry/XcodeBuildMCP/issues/492) · 2026-07-24 · open · external user · 2 comments

The remaining reports are on [the project's issue tracker](https://github.com/cameroncooke/XcodeBuildMCP/issues).