You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Open in Xcode does nothing when Xcode is installed as Xcode-beta.app #6159
open -a resolves via LaunchServices by app name, and a beta Xcode is installed as Xcode-beta.app, so the lookup fails:
$ open -a "XCode" ios/Runner.xcworkspaceUnable to find application named 'XCode'
$ echo$?1
The safeToolSpawn result isn't checked, so nothing surfaces in the UI — the context-menu item just appears to do nothing. The .xcworkspace/.xcodeproj discovery above it works correctly; only the launch fails.
This affects anyone on an iOS/macOS beta, who generally cannot install a stable Xcode alongside it for the current SDK.
To Reproduce
Have /Applications/Xcode-beta.app as the only installed Xcode (no /Applications/Xcode.app).
Open a Flutter project.
Right-click the ios folder in the explorer → Open in Xcode.
Nothing happens, and no error is shown.
Expected behavior
Xcode opens the project, or an error is shown if it genuinely can't be found.
Proposed solution
Launch by bundle ID instead of app name. Both Xcode.app and Xcode-beta.app declare com.apple.dt.Xcode:
Verified locally (patched into the installed extension bundle) — it opens Runner.xcworkspace in Xcode beta correctly.
-b goes through the same LaunchServices database as -a, just keyed on bundle ID rather than name, so this should preserve the fix from #5420 (Xcode installed on an external drive) while also handling renamed/beta installs. It also avoids depending on open -a being case-insensitive for "XCode".
Happy to raise a PR for this if the approach looks right.
Please complete the following information:
Operating System and version: macOS 27.0 (26A5421a)
Activity