`script/macos/bootstrap` fails when Xcode is installed via Xcodes app or under a non-default name

[SagarSDagdu]

Summary

script/macos/bootstrap hardcodes a check for /Applications/Xcode.app and a sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer. This breaks for users who install Xcode via the Xcodes app, where installations are named like Xcode-26.3.0.app or Xcode-beta.app. The script exits with "Please install Xcode from the App Store before continuing." even though a fully functional Xcode is installed.

Steps to reproduce

1. Install Xcode via the Xcodes app (so it lands at /Applications/Xcode-26.3.0.app rather than /Applications/Xcode.app).
2. Ensure xcode-select -p points at that install (e.g. /Applications/Xcode-26.3.0.app/Contents/Developer).
3. Run ./script/macos/bootstrap.

Expected behavior

The script detects the existing Xcode installation (regardless of its .app filename) and proceeds.

Actual behavior

The script fails immediately at the [ -d "/Applications/Xcode.app" ] check and prints "Please install Xcode from the App Store before continuing."

Environment

• macOS, Xcode installed via Xcodes app.
• Affected file: script/macos/bootstrap (lines 8–13).

Notes

A complete fix should: (a) accept any /Applications/Xcode*.app name, (b) detect when only Command Line Tools is selected and either switch to a discovered full Xcode or fail with the intended error, and (c) preserve the existing auto-xcode-select --switch behavior so users with a full Xcode installed but CLT currently selected don't have to fix selection by hand.

[oz-for-oss]

@SagarSDagdu

Here's what I found while triaging this issue:

This looks reproducible from the current setup script: it only recognizes the default Xcode app bundle name, so Xcodes.app-managed installations can be rejected even when a full Xcode is installed. I did not find enough matching existing issues to mark this as a duplicate.

Maintainer details

I concluded that the macOS bootstrap script rejects valid full Xcode installs when the app bundle is not named /Applications/Xcode.app..

Triage summary

This is a reproducible macOS bootstrap bug. The current script/macos/bootstrap checks only for /Applications/Xcode.app before continuing, then unconditionally switches xcode-select to /Applications/Xcode.app/Contents/Developer. That matches the reported failure for Xcodes.app-managed installs such as Xcode-26.3.0.app or Xcode-beta.app, even when the selected developer directory already points at a valid full Xcode.

Likely fix area: update the Xcode detection/selection logic in script/macos/bootstrap so it can identify a full Xcode from the current xcode-select -p value or from /Applications/Xcode*.app, while still preserving the existing behavior of switching away from Command Line Tools when a full Xcode is available.

Duplicate check: I searched all open non-PR issues and recently closed issues permitted by the workflow. #9996 is related to ./script/bootstrap and Xcode, but it describes a different failure mode where bootstrap succeeds and a later build fails because the Metal Toolchain is missing. I did not find two or more matching duplicates for the Xcodes.app bundle-name issue.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz

[oz-for-oss]

This issue has been labeled ready-to-implement and is open for contributions involving code changes. If you'd like to tackle it, feel free to open a pull request against this issue. You can also comment @oz-agent on this issue to have the bot draft an implementation PR automatically.