Before submitting
Area
apps/server
Steps to reproduce
- On a Mac that has both Xcode.app and Command Line Tools installed, point the developer directory at Command Line Tools:
sudo xcode-select -s /Library/Developer/CommandLineTools. This is the state many Macs are in when Command Line Tools were installed before Xcode, or after an Xcode update reset the path.
- Open T3 Code on that Mac, go to Settings, and run the device setup.
- Turn on the device hub and go to the Simulators step.
Expected behavior
The setup should say what is really wrong: xcrun cannot find simctl because the developer directory points at Command Line Tools. It should tell the user to run sudo xcode-select -s /Applications/Xcode.app/Contents/Developer.
Actual behavior
The setup says:
Xcode is installed, but no iOS Simulator is available. Install a runtime in Xcode Settings → Components.
The runtime is already installed. The user is sent to install something they already have, and the fix that would actually work is never mentioned.
In plain terms: T3 Code checks that a program called xcrun exists and takes that to mean Xcode is ready. But the Command Line Tools ship their own xcrun that cannot run the simulator tool simctl. The device hub then asks that xcrun for the simulator list, gets an error, and returns an empty list. T3 Code sees the empty list and guesses that no runtime is installed. The hub does report the real error, but the setup wizard only shows that text when the hub itself failed to start, so the user never sees it.
Impact
Major degradation or frequent failure
Version or commit
main @ 01e05c1
Environment
macOS, Xcode 26 with iOS 26.5 runtime, T3 Code desktop app
Logs or stack traces
$ xcode-select -p
/Library/Developer/CommandLineTools
$ xcrun simctl list devices available
xcrun: error: unable to find utility "simctl", not a developer tool or in PATH
After the fix below the same command lists eleven iOS 26.5 simulators.
Workaround
Run sudo xcode-select -s /Applications/Xcode.app/Contents/Developer, then reopen the device setup. The SSH device host already runs xcrun simctl help as its check, so remote Mac hosts do not have this problem. Only the local host does.
Before submitting
Area
apps/server
Steps to reproduce
sudo xcode-select -s /Library/Developer/CommandLineTools. This is the state many Macs are in when Command Line Tools were installed before Xcode, or after an Xcode update reset the path.Expected behavior
The setup should say what is really wrong:
xcruncannot findsimctlbecause the developer directory points at Command Line Tools. It should tell the user to runsudo xcode-select -s /Applications/Xcode.app/Contents/Developer.Actual behavior
The setup says:
The runtime is already installed. The user is sent to install something they already have, and the fix that would actually work is never mentioned.
In plain terms: T3 Code checks that a program called
xcrunexists and takes that to mean Xcode is ready. But the Command Line Tools ship their ownxcrunthat cannot run the simulator toolsimctl. The device hub then asks thatxcrunfor the simulator list, gets an error, and returns an empty list. T3 Code sees the empty list and guesses that no runtime is installed. The hub does report the real error, but the setup wizard only shows that text when the hub itself failed to start, so the user never sees it.Impact
Major degradation or frequent failure
Version or commit
main @ 01e05c1
Environment
macOS, Xcode 26 with iOS 26.5 runtime, T3 Code desktop app
Logs or stack traces
After the fix below the same command lists eleven iOS 26.5 simulators.
Workaround
Run
sudo xcode-select -s /Applications/Xcode.app/Contents/Developer, then reopen the device setup. The SSH device host already runsxcrun simctl helpas its check, so remote Mac hosts do not have this problem. Only the local host does.