Xcode 13.3 spits "Requested but did not find extension point with..." on `xcodebuild -list -json`

Question

Created Apr ’22

Replies 7

Boosts 2

Views 16k

Participants 16

We use command xcodebuild -list -json to get json and parse it to do further stuff on our CI machine. But since Xcode 13.3 when I run this command in terminal I get

➜  Main git:(export-gsps-while-building-ipa) ✗ xcodebuild -list -json                               

2022-04-08 19:51:18.917 xcodebuild[27576:698981] 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-04-08 19:51:18.918 xcodebuild[27576:698981] 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

{

  "project" : {

    "configurations" : [
...

As you can see, the expected output has two warnings ahead and hence this JSON is not parsable.

Answered by MrtnFbg in 713197022

All suggested fixed did not work for me.

As a workaround I added 1>&2 2>/dev/null so the error does not show and parsing the output of -list -json is now working again.

xcrun xcodebuild -quiet -list -json 1>&2 2>/dev/null

Boost

Answer 1

czareknster OP

Apr ’22

Hi, Open Xcode and install updates. It should help.

5

Answer 2

olegiv OP

Apr ’22

Hello, this fixed the issue for me:

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

0

Answer 3

MrtnFbg OP

May ’22

Accepted Answer

All suggested fixed did not work for me.

As a workaround I added 1>&2 2>/dev/null so the error does not show and parsing the output of -list -json is now working again.

xcrun xcodebuild -quiet -list -json 1>&2 2>/dev/null

2

Answer 4

AlphaBo OP

May ’22

This worked for me:

Remove CommandLineTools

sudo rm -rf /Library/Developer/CommandLineTools

Reinstall CommandLineTools

xcode-select --install

Select CommandLineTools

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

1

Answer 5

ReaddyEddy OP

Jun ’22

I saw the issue after updating Xcode, launching it and updating the command line tools. I restarted my machine (a rarity these days) problem resolved. I suspect the paths are not reloaded after the command line tools are installed so the restart resolved the issue. So less drastic options are re-launching terminal or reloading the environment in he terminal.

0

Answer 6

dinesh_hudinwal OP

Jun ’22

MrtnFbg's answer inspired me to read more about redirections of streams. So I read about Linux STDOUT STDERR. In this specific case when I run this command, there is an output and there are some errors. Since I ran this command on terminal and on terminal the STDOUT and the STDERR is the console itself hence, I was seeing both the json and the errors.

I now don't see an issue with the Xcode 13 or the command itself.

I need to update the way I am consuming this command. Since I am interested only in the output of the command hence it should have been xcodebuild -list -json 2>/dev/null where I am redirecting 2(the error stream) to a file that just eats up whatever it gets(the /dev/null file)

0

Answer 7

dorocode OP

Sep ’22

Guys if you're facing this problem on flutter, just remove all your flutter SDk files and download them again. git clone https://github.com/flutter/flutter.git -b stable

0