Skip to content
Latchkey

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 PATH

Common 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

  1. Point xcode-select at the Xcode.app on the runner.
  2. Verify the active path before building.
shell
sudo xcode-select -s /Applications/Xcode.app/Contents/Developer
xcode-select -p

Confirm 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

Tired of flaky CI? Latchkey auto-heals failed jobs and retries them for you. Start free →