xcrun "unable to find utility" in CI
xcrun looks up a tool in the active developer directory and cannot find it, usually because the active directory points at the bare Command Line Tools rather than a full Xcode.
What this error means
A build or tooling step fails with xcrun: error: unable to find utility "...". The runner has Command Line Tools selected but the utility ships only with full Xcode.
xcodebuild
xcrun: error: unable to find utility "simctl", not a developer tool or in PATHCommon causes
Command Line Tools selected instead of Xcode
Utilities like simctl and many SDK tools live inside Xcode.app, not the standalone CLT package.
Wrong or missing Xcode path
The active developer directory points at a path that does not contain the requested tool.
How to fix it
Select a full Xcode toolchain
- Point xcode-select at the Xcode.app on the runner.
- Verify the active path before building.
shell
sudo xcode-select -s /Applications/Xcode.app/Contents/Developer
xcode-select -pConfirm the tool exists in that Xcode
Run xcrun --find <tool> to check the resolved path; if it is missing, the selected Xcode version may be too old or wrong.
How to prevent it
- Pin and select a known Xcode version at the start of the job. On managed runners this is part of the macOS image; standardize the xcode-select step across jobs.
Related guides
xcodebuild "requires Xcode" (Command Line Tools only) in CIFix the xcodebuild "requires Xcode, but active developer directory is a command line tools instance" error in…
xcodebuild "module map file not found" in CIFix the xcodebuild "fatal error: module map file not found" error in CI by regenerating Pods or clearing deri…
xcodebuild "Command PhaseScriptExecution failed" in CIFix xcodebuild "Command PhaseScriptExecution failed with a nonzero exit code" in CI by reading the run-script…