Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

xcrun cannot find simctl on a Mac with Xcode

Errorxcrun: error: unable to find utility "simctl", not a developer tool or in PATH

Short answer

simctl ships only inside Xcode, not in the Command Line Tools package. The error means xcrun looked in a developer directory that has no simctl. Point xcode-select at your Xcode app and finish Xcode's first-launch setup.

  • Applies to Xcode 26, macOS 26
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Print the active developer directory. If it is /Library/Developer/CommandLineTools, xcrun is not looking inside Xcode.

    xcode-select -p
  2. 2Match what you see, then jump to its fix

    1. 1xcode-select -p prints /Library/Developer/CommandLineToolsThe active developer directory is the Command Line ToolsFix
    2. 2Xcode is selected, but the tool is still missing or Xcode says components are requiredXcode's first-launch components are not installedFix

What does the error look like?

  • xcrun: error: unable to find utility "simctl", not a developer tool or in PATH

Cause 1 of 2

The active developer directory is the Command Line Tools

1Check

Apple says simctl is one of the tools that only ship with the Xcode app, and that you must set Xcode as the active developer directory before using them.

xcode-select -p

2Fix

Switch to the Xcode app. This needs administrator rights and affects all users.

sudo xcode-select -s /Applications/Xcode.app

3Verify

xcrun finds the tool.

xcrun --find simctl

Confirmed by developer.apple.com

Did this fix it?

Cause 2 of 2

Xcode's first-launch components are not installed

1Check

Apple documents that running xcodebuild -runFirstLaunch installs the required system components, including the simctl utility. The status command shows whether any first-launch work is pending.

xcodebuild -checkFirstLaunchStatus; echo $?

2Fix

Run the first-launch step for the selected Xcode.

sudo xcodebuild -runFirstLaunch

3Verify

simctl lists simulator runtimes.

xcrun simctl list runtimes

Confirmed by developer.apple.com

Did this fix it?

How do I stop it coming back?

  • After installing or updating Xcode, run xcode-select -s once and the first-launch step.
  • On build machines pin the Xcode path in the job setup, not in the image default.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Related fixes

Mobile apps

App record creation fails because you lack permission

You cannot add a new app in App Store Connect as a Developer or limited user

Only the Account Holder, an Admin or an App Manager can create an app record, and Apple blocks it until the Account Holder has signed the latest agreement.

3 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.