Xcode Error When Launching Terminal

Question

I'm getting the following errors when launching my terminal, seemingly out of nowhere. I have no idea what the cause is.

2022-03-23 09:41:00.818 xcodebuild[2352:21059] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionSentinelHostApplications for extension Xcode.DebuggerFoundation.AppExtensionHosts.watchOS of plug-in com.apple.dt.IDEWatchSupportCore

2022-03-23 09:41:00.818 xcodebuild[2352:21059] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionPointIdentifierToBundleIdentifier for extension Xcode.DebuggerFoundation.AppExtensionToBundleIdentifierMap.watchOS of plug-in com.apple.dt.IDEWatchSupportCore

Does anybody know how I can go about fixing this please?

What is your default shell and what is in your shell startup files? — mmmmmm, Mar 23 '22 at 09:53
I have somilar messages now and then. Sometimes it helps to rerun xcode-select. — nohillside, Mar 23 '22 at 10:42
I'm having the same error Today for the first time ever. And I use the Iterm2 terminal almost every single day. — Reinier Garcia, Apr 04 '22 at 12:27
@nohillside I have this message every first run of my terminal. And no, xcode-select definitely does NOT solve it. — sovemp, Apr 08 '22 at 23:24

score 71 · Answer 1 · answered Mar 27 '22 at 19:00

71

Neither "installing components" via Xcode, nor resetting the developer directory using sudo xcode-select -r worked for me. However,

sudo xcode-select -s /Library/Developer/CommandLineTools

worked. Thanks to Royite on Apple's Developer Forums for this solution.

answered Mar 27 '22 at 19:00

Sagar

881

2

this worked for me, for Xcode 13.3 macOS 12.2.1 (21D62), iterm2 – Sajjon Apr 06 '22 at 12:36
3

I had to sudo rm -rf /Library/Developer/CommandLineTools then sudo xcode-select --install, and that fixed the issue for me. (Got the recommendation hint from brew doctor.) – Eljay Apr 09 '22 at 14:32
After I did this, I could no longer run xcrun xcodebuild from the command line. brew doctor says everything is fine. However, terminal and most command line tools run fine (thanks to sudo xcode-select -r). However xcrun xcodebuild generates both this error and another about "Class ... is implemented in both ...". – mm2001 Apr 23 '22 at 05:25
worked for me, Xcode command line tools on macOS v12.3.1 – cenk Apr 29 '22 at 14:23
Also received warning: Usage of /Users/me/Library/org.swift.swiftpm/collections.json has been deprecated. Please delete it and use the new /Users/me/Library/org.swift.swiftpm/configuration/collections.json instead. As advised, delete of the deprecated file obviated the warning. – Max MacLeod Sep 20 '22 at 12:38

Terrabits · Accepted Answer · 2022-04-11T18:44:32.843

28

This happens with XCode after every upgrade.

So, like @Eljay, I placed the following commands in a script, upgrade-xcode-cli-tools, which I call after each XCode upgrade:

#!/usr/bin/env bash
remove old CommandLineTools
to force upgrade
sudo rm -rf /Library/Developer/CommandLineTools
install latest
sudo xcode-select --install

Note that the script will cause a pop-up that requires user participation (e.g. accepting EULA). I am not aware of any way around this.

edited Apr 11 '22 at 18:44

answered Apr 11 '22 at 16:39

Terrabits

404

3

Warning: The install this requires is extremely slow (~3 hours on a 15mb/s connection). Make sure you can wait. – Nick Bailey Jul 20 '22 at 17:20
For me it took only 30min. It would depends on your network speed. – Ezeewei Sep 07 '22 at 14:23

score 18 · Answer 3 · answered Mar 24 '22 at 17:26

18

This happened to me after an Xcode version update. Running XCode app and letting it re-install components resolved the issue.

answered Mar 24 '22 at 17:26

Jas

281
1
3

1

What do you mean by "letting it re-install components?" Did this happen automatically, or did you have to select a menu item or otherwise trigger it? – Brandon Lewis Mar 31 '22 at 21:27
2

Should happen automatically when running XCode first time after update. (Unless XCode is somehow "stuck") – Jas Apr 01 '22 at 22:12

score 9 · Answer 4 · answered Apr 04 '22 at 12:32

9

Solution:

Close the terminal (it was Iterm2 in my case).
Just open Xcode.
It will request to instal additional components. Press on 'Install'.
When it ends, close XCode.
Open the terminal again. No more error messages.

answered Apr 04 '22 at 12:32

Reinier Garcia

199
3

score 2 · Answer 5 · answered Jul 10 '22 at 16:28

Running each one of these commands twice fixed it for me. This outputs your current sdk paths.

The errors appear on the first run, and after the second run, they magically disappear for good.

xcrun -sdk iphoneos --show-sdk-path
xcrun -sdk iphoneos --show-sdk-version
xcrun -sdk iphoneos --show-sdk-build-version
xcrun -sdk iphoneos --show-sdk-platform-path
xcrun -sdk iphoneos --show-sdk-platform-version
xcrun -sdk macosx --show-sdk-path
xcrun -sdk macosx --show-sdk-version
xcrun -sdk macosx --show-sdk-build-version
xcrun -sdk macosx --show-sdk-platform-path
xcrun -sdk macosx --show-sdk-platform-version
xcrun -sdk watchos --show-sdk-path
xcrun -sdk watchos --show-sdk-version
xcrun -sdk watchos --show-sdk-build-version
xcrun -sdk watchos --show-sdk-platform-path
xcrun -sdk watchos --show-sdk-platform-version

Source: https://stackoverflow.com/questions/71320584/flutter-build-ios-got-error-requested-but-did-not-find-extension-point-with-ide

score -1 · Answer 6 · answered Jun 06 '22 at 07:31

-1

The easy solution is if you are building react native app. just run the command below.

react-native run-ios

answered Jun 06 '22 at 07:31

Mizanur Rahman

1

The question is about Xcode errors in Terminal. Can you explain how the command you propose solves those? – nohillside Jun 06 '22 at 07:36

Xcode Error When Launching Terminal

6 Answers6

remove old CommandLineTools

to force upgrade

install latest

Linked