Git is not working after macOS update ("xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools")

D

41

3470

I updated to the latest OS, and/or restarted my computer (this happens on every major update, but this time all I did was restart my computer on 2022-09-13).

This morning I navigated to my work's codebase in the command line on my MacBook Pro, typed in "git status" in the repository and received an error:

(In 9/2022, this error was much different, but I didn't capture it)

xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun

Git will not work!

How do I fix Git, and the command-line tools?

Dedie answered 26/9, 2018 at 16:43 Comment(24)

This is more of a git problem than a macOS problem. – Dedie 14/1, 2019 at 6:17

Possible duplicate apple.stackexchange.com/questions/254380/… – Doglike 1/7, 2019 at 5:28

to be honest, this problem is something APPLE should take care of. They create it, they should fix it !!!!! Asking everyone to run that command everytime this happens isn't an Good/Correct option. Not to mention you need to download that big chunk for git only. – Arnulfoarny 4/2, 2021 at 14:30

I didn’t run into it on my update to Big Sur. Only had this problem the year when I originally wrote this Q&A. I’ve just been updating it every year to include the latest changes. – Dedie 5/2, 2021 at 5:7

If you don't have Xcode, only installing Xcode command line tools will solve the problem. developer.apple.com/download/more/?=command%20line%20tools – Jowl 8/2, 2021 at 9:18

alianjum0, thanks for that. I just went down a huge rat hole being unable to install XCode from the AppStore (long story). Being able to install just the CLI saved the day! – Misdirection 13/3, 2021 at 2:2

We should get paid by apple for debugging their code! – Millian 1/4, 2021 at 9:46

It's a failure to completely update ALL their software during a major version update. I have not run into this since i initially made the question and answer! So it works on some level i suppose! – Dedie 1/4, 2021 at 13:33

@Dedie No. It's not a problem with git. It's a macOS problem. You get the same error from other commands like make. The solution is what I thought it was but I checked here anyway as I wanted to be sure - too much going on to worry about possible fixes. – Adjoin 26/10, 2021 at 14:48

Another OS update and yet 3 years later, issue still exist. – Sextet 2/11, 2021 at 8:50

I updated to Monterey and faced the same issue. Apple really needs to look into this issue. – Enlarge 2/11, 2021 at 23:37

I never had this issue before and I've been using macOS since about the last 3 years. However I just updated it to Monterrey and it broke git. – Tyika 11/11, 2021 at 14:27

"This is more of a git problem ..." how so? git is merely a command line tool. I've used git on other platforms for decades and have never encountered this issue until working on a Mac. What the hell does git have to do with XCode? – Hertz 16/12, 2021 at 15:52

I wrote that 3 years ago matey! lol But yea. it's totally a macOs problem. I did not think this would be a relevant for 3 years! – Dedie 17/12, 2021 at 20:8

Is there some issue/ticket in an Apple help system that we can upvote to try to get more attention on this? – Torquemada 26/1, 2022 at 17:7

No need to download Xcode. I am using MacOS Monterey version 12.x. I have downloaded "Command Line Tools for Xcode 13.3 beta". Restarted terminal and command line is working along with github clone/pull/push issues. It worked like charm. – Farthest 5/2, 2022 at 9:10

Again the same problem with Ventura! Come on, Apple! – Outgeneral 27/10, 2022 at 13:30

I'm also having the same problem with Ventura @Upendra. If this happens with every macOS update (it breaks Git), it would be nice if someone could at least write a nice blog post about this... – Misapprehend 31/10, 2022 at 22:29

I had the problem with Ventura as well. Solution for me was to launch the Xcode app once. – Axis 2/11, 2022 at 10:42

Every year around fall i got a huge surge of rep from this Q and A. you'd think developers would be the one group of folks they want to make happy. I think some of my counter answers are right. Switch to Brew, forget about this problem forever! I do like the simulate phone feature of xocde. I think that's worth having, but other than that, i do not need x-code! – Dedie 13/12, 2022 at 14:59

apple somehow seems to be discouraging developers to use a mac without xcode ! this is outright monopilistic behaviour. The only thing apple is notorious for. – Kravits 5/1, 2023 at 11:55

All hail the apple and its PITA git! lol – Dedie 6/1, 2023 at 13:16

Thank you Creator for Stack Overflow! I got this issue when I just upgraded to Sonoma... installed v15.1 and worked like a charm. – Peggy 9/1 at 18:48

Agreed! What a great community this is! CasaCoding! – Dedie 28/3 at 15:56

D

5051

The problem is that Xcode Command-line Tools needs to be updated due to a MacOs update.

Did not run into this on Sonoma.
- Maybe Apple fixed the process?
Updated for Ventura

After opening the terminal after restarting, I tried to go to my code, and do a git status, and I got an error and prompt for command line software agreement:

So press space until you get to the [agree, print, cancel] option, so careful hit space to scroll down to the end, if you blow past It you have to run a command to get it back. Use sudo xcodebuild -license to get to it again.

Just be careful on scrolling down and enter agree and press return and it will launch into an update.

Then I tried to use git after the install, and it prompted me to install Xcode tools again.

I followed my own advice from previous years (see below), and went to https://developer.apple.com/download/all and downloaded "Command Line Tools for Xcode 14" (You have to log in with your Apple ID and enter MFA code, so have all the devices you need for that handy. Then select "Command Line Tools for Xcode 14", or if you want to get into the alphas or betas, that's up to you. But stable releases are probably the best choice for software developers.

You have to either download the tools from CLI or the developer page and before you can use git, you need to reboot!!! Or you will get stuck in a loop of prompt & downloading

Rebooting will break the loop and complete the installation of your CLI tools including git so that you can get back to work

Solutions for previous years, these may or may not be valid these days as the downloads page has changed significantly:

PREVIOUS YEARS SOLUTIONS, probably #2 is most helpful.

*** Solution #1:

Go back to your terminal and enter:

xcode-select --install

You'll then receive the following output:

xcode-select: note: install requested for command line developer tools

You will then be prompted in a window to update Xcode Command Line tools. (which could take a while)

Open a new terminal window and your development tools should be returned.

Addition: With any major or semi-major update you'll need to update the command line tools in order to get them functioning properly again. Check Xcode with any update. This goes beyond Mojave...

After that restart your terminal

Alternatively, IF that fails, and it might.... you'll get a pop-up box saying "Software not found on server", proceed to solution 2.

*** Solution #2: (Preferred method)

If you hit xcode-select --install and it doesn't find the software, log into Apple Developer, and install it via webpage.

Log in or sign up here:

https://developer.apple.com/download/more/

Look for: "Command Line Tools for Xcode 14.x" in the list of downloads Then click the dmg and download. (See previous image above) either way, you will probably wind up at an apple downloads webpage.

Dedie answered 26/9, 2018 at 16:43 Comment(63)

This fixed the issue I had with Microsoft Visual Studio Code which was complaining about Git not being installed when I first launched it after upgrading to Mojave. I thought the issue was VS Code, but it was the issue in this SO question. Restarting VS Code after installing the Xcode Command-line Tools solved the issue. – Anarthria 10/10, 2018 at 0:36

I wish the Xcode update was part of the OS update. Something like this happens every time I upgrade. Annoying. – Octoroon 14/12, 2018 at 17:17

It's happened to me on every update. I guess the majority of Mac users don't have Xcode installed! Otherwise apple probably would update it at the same time. . – Dedie 14/12, 2018 at 18:19

Definitely annoying though. A simple check for Xcode installation and then an update during the OS update would be pretty simple to add. It's always something with these OS updates from Apple. You'd think they'd have figured it out by now. – Sloven 14/12, 2018 at 20:53

In case you installed GIT and this is still not working you might need to add an alias: sudo xcode-select -s /Library/Developer/CommandLineTools – Hardison 30/12, 2018 at 16:52

I'd already visited the App Store, and it claimed to find no updates. Why can't it recognize that Xcode needs to be updated? – Promissory 28/1, 2019 at 13:16

For anyone using Git in PHPStorm; you need to restart PHPStorm after running xcode-select --install. Then it'll work. – Tensiometer 13/2, 2019 at 7:20

Same SVN issue got fixed by this method as well. – Sabadell 14/5, 2019 at 17:27

When I go to install (after agreeing to T's & C's) I get "Can't install the software because it is not currently available from th Software Update server." Has anyone else gotten this? – Juneberry 6/6, 2019 at 12:52

I did not need to restart my terminal btw. – Idolum 7/6, 2019 at 16:38

Nothing is working for me. I am using Sourcetree on same repository. it shows the username and email correctly. – Delectable 15/6, 2019 at 7:33

For me running open /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg after the xcode-select --install command worked, following this stackoverflow answer – Accoutre 27/8, 2019 at 18:23

This solution works for me for Mac Catalina update also. Superb!!! – Bolin 8/10, 2019 at 16:55

I updated the text to just say "MacOs update" I am very happy it works for Catalina! Figured it would! – Dedie 10/10, 2019 at 1:30

just wanted to add that you need to restart the computer, also a good brew doctor may also help find any issues – Uvulitis 14/11, 2019 at 16:27

I am using android studio on Mac, recently updated OS to Catalina. After updating OS, stop connecting to Version Control (subversion). But thanks to @dustbuster, installing xCode solve the my problem. – Horseshit 23/11, 2019 at 10:54

But why ? Why do we need to do this ? my question is to Apple falks – Fierro 19/12, 2019 at 10:48

Should I do the same with zsh too ? – Siftings 23/12, 2019 at 8:40

You will not have to do anything to zsh Tilak. The issue is git. Not zsh. – Dedie 23/12, 2019 at 18:5

After the update , you need to make sure to restart all the applications and IDE that depend or have connection with git like all IntelliJ IDEs ,sublime with git , source tree etc to make it run properly, – Pumpkin 25/12, 2019 at 11:30

If you have Xcode installed, you do not need the separate command line tools install. Just make sure you run xcode-select --switch /Applications/Xcode.app/Contents/Developer or xcode-select --reset so Terminal will use the command line tools inside Xcode instead of the ones installed by the "command line tools" standalone installer. From then on, the App Store will auto-update Xcode and your tools will stay current. – Sclerite 15/2, 2020 at 10:50

July 2020 Update: This answer worked for me on Mac OS Mojave (after upgrading from El Captain). Takes a while to install though. (Just doing xcode-select --reset as mentioned in other answers did not work for me) – Randy 7/7, 2020 at 7:38

The way apple manages the xcode downloads has changed. I actually ran into this myself AGAIN when i upgraded this year! So i updated the answer not too long ago. – Dedie 22/10, 2020 at 18:26

For PyCharm also need to do like PHPStorm as suggested by @DaanvandenBergh . That is need to restart PyCharm after running xcode-select --install – Spurrier 8/11, 2020 at 6:42

Upgraded to macOS Big Sur and here it is again. – Shawana 17/11, 2020 at 10:40

I have updated this answer every year! Check out solution #2, that's probably the most relevant. There's a surge this time every year! – Dedie 17/11, 2020 at 16:49

I had to download Command_Line_Tools_for_Xcode_12.3_beta.dmg for MacOS 11.1 Big Sur. Then it worked perfectly. – Orlena 24/11, 2020 at 9:26

Glad to hear! I have not updated yet. is that the name of the download file now? – Dedie 30/11, 2020 at 19:52

thanks a lot! I immediately went for solution 2 once I read that solution 1 might very well fail haha. – Apheliotropic 5/1, 2021 at 10:42

Most Excellent! I actually didn't run into it this time around when I updated to Big Sur. – Dedie 5/1, 2021 at 19:39

How could Git is not part of OSX? If not, then make it never part of OSX? what's the benefits of bundling a developer tool in the operation system which is not responsible for updating it? – Arnulfoarny 4/2, 2021 at 14:29

Awesome! Solution #1 works for me. Thanks :) It's so annoying to do this after every minor update. Techies at Apple Listen O Listen !! – Orji 14/3, 2021 at 15:6

You should not have to do it after every update, that is annoying!! – Dedie 15/3, 2021 at 12:7

I update Xcode to Version 12.5 (12E262), which is the latest one. And I get this same error. Does it means I need to do xcode-select --install each time manually? – Rivalry 30/4, 2021 at 10:55

xcode-select --install + terminal restart fixed broken git after Catalina -> Big Sure update! – Dimercaprol 13/5, 2021 at 12:16

Solution 1 worked for me running macOS 11.5.1. Thank you :D – Halonna 16/8, 2021 at 21:57

on the update to monterey, it worked like a charm (xcode-select --install). Thank you so much!! – Tupiguarani 1/11, 2021 at 12:50

I updated from macOS Big Sur -> macOS Monterey, Nov 01, 2021. Same problem with git:

xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun

. This installation solved the problem: xcode-select --install THANK YOU!!! – Leninakan 2/11, 2021 at 1:11

I cannot believe this problem has not been solved in November 2021. Apple WTH? – Trawl 13/11, 2021 at 21:32

I updated recently to MacOS Monterey , and this update of xcode tools was able to fix this exact same issue. Thank you. – Redo 21/12, 2021 at 19:47

No need to download Xcode. I am using MacOS Monterey version 12.x. I have downloaded "Command Line Tools for Xcode 13.3 beta". Restarted terminal and command line is working along with github clone/pull/push issues. It worked like charm. – Farthest 5/2, 2022 at 9:11

I never understood why XCode is required for git or why it interferes with my git installation in the first place. I tried to uninstall Xcode completely to avoid this situation, but that did not work out well – Rebozo 7/3, 2022 at 0:58

For iOS Monterey, I went with 13.3.1. And git started working again. – Underhanded 11/4, 2022 at 21:38

Works perfect with macOS Catalina – Geomancer 5/5, 2022 at 3:50

My first dev job was in .Net. I remember thinking Visual Studio was huge and invasive. It's got nothing on Xcode. – Messaline 31/5, 2022 at 2:53

Yep I feel the same way! I learned how to code in college using Visual Studio. Now if I accidentally double click a file that's registered to open with Xcode I go right for the force quit! Do not pass go and no 200 bucks for you! – Dedie 1/6, 2022 at 13:56

I recently upgraded to Monterey 12.5 and I did not need to restart my iterm2 so maybe add a step to check before restarting – Castara 10/8, 2022 at 17:26

The first option requires 15GB of space to install. any other way? – Brower 23/8, 2022 at 9:52

Deja vu, wow. Every bigger Mac update I'm back here... This should get fixed at some point. – Wigeon 25/8, 2022 at 9:7

This worked for me after the macOS Ventura 13.0 update. – Gammon 25/10, 2022 at 23:11

All I had to do was to go to Xcode - Preferences - Locations and select the Command Line Tools from the dropdown that was empty, after updating to macOs Ventura. – Gurias 27/10, 2022 at 12:52

@Octoroon I'm so confused why xcode wouldn't update with a macOS update. Isn't xcode also produced by apple? developer.apple.com/xcode – Misapprehend 31/10, 2022 at 22:35

You don't have to update Mac to update Xcode, when you update macOS first, like to Montery, you have to update Xcode. – Dedie 1/11, 2022 at 13:9

Wow, I'm stuck without git on my mobile data plan (on a trip). I don't use any Apple dev tools. This is embarrassing... – Pulsatile 5/3, 2023 at 10:42

Damien Maybe Install git using brew. Much less downloading! I think how to do that is below somewhere! – Dedie 7/3, 2023 at 15:22

Your link "developer.apple.com/download/all/?q=Command%20Line%20Tools" is actually linked to "developer.apple.com/download/more" And your text says download "Command Line Tools" but the screenshot highlight "Additional Tools" – Houseyhousey 8/3, 2023 at 10:58

Image and link updated ^^ stuff changes at developer.apple all the dang time! – Dedie 8/3, 2023 at 15:31

Along with this great answer, I had to follow the advice on this post first, then I was able to run the xcode-select --install: #55939854 – Darceydarci 20/6, 2023 at 20:59

This Q & A has gotten me nearly 80K in rep! Thanks to all for the upvotes! I love you all! – Dedie 30/6, 2023 at 16:36

If anyone runs into this on Sonoma, please. add an update. I did not run into any issues this go around. maybe Apple fixed the problem? – Dedie 3/10, 2023 at 14:35

Had this issue still in MacOS Sonoma Version 14.1 (23B74) and got it resolved using the xcode-select --install option, thanks! – Resorcinol 3/11, 2023 at 17:40

Awesome! I did not run into it with Sonoma. Glad it still worked! – Dedie 6/11, 2023 at 17:21

None of the command line inputs worked but going to the website and downloading the latest stable release fixed it right up!!! A'hehee!!! – Peggy 9/1 at 18:49

M

384

I got some errors that the software was unavailable from the update server when trying

xcode-select --install

What fixed it for me was going here https://developer.apple.com/download/more/ and downloading Command Line Tools (macOS 10.14) for Xcode 10 and then installing it manually.

After that, the errors should be gone when you open up a new terminal.

Update for macOS Ventura 13.0.1 (Nov 2022)

Install Command Line Tools for Xcode 14.1

Missionary answered 31/10, 2018 at 17:33 Comment(11)

This should be the right answer, tried on 3 machines and @Dedie answer doesn't work anymore and it shows "software was unavailable from the update server when trying" – Yseulta 2/11, 2018 at 14:17

For me this ends with software not available at server but @High6's answer below works. xcode-select --reset – Fatso 4/11, 2018 at 14:59

downloading Command Line Tools (macOS 10.14) for Xcode 10.1 from the link. thanks! – Afflict 4/11, 2018 at 21:33

Had xcode installed still there were issues. This worked like a charm... should be the selected answer. Or should be addendum to top answer. – Maximin 22/11, 2019 at 11:43

This also works for macOS 10.15.2. Though I had to select Command Line Tools for Xcode 11.3, since Xcode 10.1 wasn't available – Laveta 13/12, 2019 at 21:4

On Mac OS 10.15.6 Catalina, this was the solution that worked for me. (Command Line tools for Xcode 12 if you're on Catalina - skip the mammoth Xcode 12 app download) – Alligator 21/9, 2020 at 16:25

Resolved same issue for me. – Myrt 14/11, 2022 at 15:59

On macOS Ventura 13.0.1, this also resolved for me by installing Xcode from the App Store. – Alfreda 30/11, 2022 at 9:3

Your update for macOS Ventura helped me out. It seems, that even restarting is unnecessary. – Koel 2/12, 2022 at 0:5

Above command itself worked for Vetura as well without restarting – Phosphene 29/12, 2022 at 9:31

Even though I was able to xcode-select --install for Ventura, I was not able to push anything. Downloading the command line tools pkg installer did work for me. – Spanking 27/3, 2023 at 13:29

O

181

For me xcode-select --reset was the solution on Mojave.

Olmsted answered 31/10, 2018 at 18:1 Comment(13)

somehow, "xcode-select --install" ends of software not available at server. But this one works – Opportuna 1/11, 2018 at 4:32

This worked for me, I ran this command after installed new Xcode. – Singlephase 24/9, 2019 at 2:1

I just upgraded from Mac OS X 10.14 (Mojave) to MacOS 10.15 (Catalina) and faced this problem, this solution worked fine, it was no necessary to run xcode-select --install. – Moraceous 22/10, 2019 at 22:19

works for me on Catalina as well, but needed to add sudo – Brandie 6/11, 2019 at 10:58

sudo xcode-select --reset worked for me on a Mojave --> Catalina upgrade of MacOS – Ram 12/12, 2019 at 15:34

2020 Update: Same solution for Catalina OS – Greer 7/6, 2020 at 16:35

July 2020 Update: This did not work on Mac OS Mojave (after upgrading from El Captain). This worked from the accepted answer: xcode-select --install. Takes a while to install though – Randy 7/7, 2020 at 7:36

Does not work for Catalina. sudo xcode-select --reset appears to do nothing. – Scofield 28/9, 2020 at 7:18

I needed to run this command after I migrated from old Mojave MBP to new Catalina MBP and couldn't have git etc running; intellij complained – Jagged 9/10, 2020 at 9:22

This did not work on Monterey. – Stan 26/10, 2021 at 18:27

Had a same problem and this works :) – Orji 9/12, 2021 at 10:36

Update 2022: works on Darwin 21.4.0 – Equestrian 24/4, 2022 at 21:33

Worked for me on Ventura – Homesick 10/11, 2022 at 7:6

D

113

In addition to dustbuster's answer I needed to set path to the Xcode folder with this command:

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

Darrickdarrill answered 11/10, 2018 at 13:55 Comment(4)

Yep same for me, @Dedie might be a good idea to merge these answers. – Juneberry 19/10, 2018 at 19:30

Ok this one solved this for me. Tried xcode-select --install and downloading and installing manually, none of the solutions worked. Note that I waited and upgraded to version 10.14.1. – Clari 19/11, 2018 at 17:38

If you have Xcode installed, you do not need the separate command line tools install. Just make sure you run xcode-select --switch /Applications/Xcode.app/Contents/Developer or xcode-select --reset so Terminal will use the command line tools inside Xcode instead of the ones installed by the "command line tools" standalone installer. From then on, the App Store will auto-update Xcode and your tools will stay current. – Sclerite 15/2, 2020 at 10:51

been through so many answers, this is the one that worked for me after the Mojave update, thanks! – Tucket 27/8, 2020 at 23:27

D

95

updated from Mojave to Big Sur and got the same error : the command

xcode-select --install

worked like a charm

Divestiture answered 21/1, 2021 at 14:0 Comment(0)

L

65

After upgrade to Mac Catalina I faced the same issue, I had to run couple of commands to get this fixed.

First started with:

xcode-select --install

It didn't fix the problem, had to run the following in sudo

sudo xcode-select --reset

Then, finally got fixed after I switched and set the path explicitly for active developer directory:

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

Note: In case you have Xcode installed, you may need to specify Xcode directory in this case, it should be something like this

xcode-select -s /Applications/Xcode.app

Leucocytosis answered 28/1, 2020 at 22:14 Comment(3)

If you have Xcode installed, you do not need the separate command line tools install. Just make sure you run xcode-select --switch /Applications/Xcode.app/Contents/Developer or xcode-select --reset so Terminal will use the command line tools inside Xcode instead of the ones installed by the "command line tools" standalone installer. From then on, the App Store will auto-update Xcode and your tools will stay current. – Sclerite 15/2, 2020 at 10:58

Xcode select did it since I only had the beta version installed! – Carlson 9/8, 2020 at 18:0

Try sudo xcode-select --reset first then --install – Stomy 23/11, 2021 at 14:19

F

54

For me what worked is the following:

sudo xcode-select --reset

Then like in @High6's answer:

sudo xcodebuild -license

This will reveal a license which I assume is some Xcode license. Scroll to the bottom using space (or the mouse) then tap agree.

This is what worked for me on MacOS Mojave v 10.14.

Fatso answered 4/11, 2018 at 15:3 Comment(4)

your solution worked for me on MacOS 10.13 High Sierra. Thank you. – Chokecherry 1/1, 2020 at 19:46

If you have Xcode installed, this is the correct solution. Terminal will use the command line tools inside Xcode instead of the ones installed by the "command line tools" standalone installer. From then on, the App Store will auto-update Xcode and your tools will stay current. – Sclerite 15/2, 2020 at 10:54

This is working for BigSur as well as the Monterey beta branch. Way easier than downloading and installing giant new Xcode releases each time you update. – Afterworld 30/7, 2021 at 22:15

This did the trick for me and fixed VSCode not finding Git after I migrated from my old iMac running Catalina to my shiny new Apple Silicon MacBook Pro running Monterey via Migration Assistant. – Vivisection 13/11, 2021 at 9:30

S

54

If you use xcode then install it (~12GB)

xcode-select --install

Otherwise install latest command line tools (~500MB)

Update: If struck in install loop

xcodebuild -runFirstLaunch

Schmit answered 14/3, 2021 at 4:15 Comment(1)

I've (re)installed xcode so many times over the past 2 years that it's like "How many times do I have to teach you this lesson, old man?" – Sphenoid 2/7, 2021 at 2:6

P

53

if there are several versions, select one of them from: xcode -> Preferences and tap Locations then select, as the followng image

Proliferation answered 3/7, 2019 at 15:31 Comment(7)

This fixes a couple items, but not all – Trapezoid 13/8, 2019 at 18:20

I had Xcode 10.3, 11.1 and 11.2 and Xcode wasn't able to figure out which version to use for the Command Line Tools and left the dropdown with empty. Once 11.1 was selected for my purpose, git commands started to work. – Scandic 18/11, 2019 at 23:34

This popup is equivalent to calling xcode-select --switch with the path to the Xcode package of whatever version you select here, by the way. – Sclerite 15/2, 2020 at 10:55

Good hint thank you , Whatever the way , the important thing is to solve the issue – Proliferation 6/4, 2020 at 13:54

This works for me.. Thanks a lot. I was having old and new version of Xcode at different locations. – Samuella 13/4, 2020 at 10:35

downvoted: you must understand the installing xcode is what is the worst option. Why should we be forced to installe 600MB of xcode just to enable the path of an already installed git? – Kravits 5/1, 2023 at 11:48

This is great way, without using xcode-select --install I chose only this path by xcode gui. – Lubra 15/9, 2023 at 6:23

L

52

I've used xcode-select --install given in the accepted answer in previous major releases.

I've just upgraded to OS X 10.15 Catalina and run the Software Update tool from preferences again after the OS upgrade completed. The Xcode utilities update was available there, which also sorted the issue using git which had just output xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools)

Laudable answered 10/10, 2019 at 8:55 Comment(1)

If you have Xcode installed, you do not need the separate command line tools install. Just make sure you run xcode-select --switch /Applications/Xcode.app/Contents/Developer or xcode-select --reset so Terminal will use the command line tools inside Xcode instead of the ones installed by the "command line tools" standalone installer. From then on, the App Store will auto-update Xcode and your tools will stay current. – Sclerite 15/2, 2020 at 10:52

C

48

I figured out the Xcode Command Line Tools part from the error message, but after running Xcode and getting the prompt to install the additional tools it did claim to install them, but still I got the same error after opening a new terminal.

So I did the xcode-select --install manually and after that it worked for me.

Clack answered 2/10, 2018 at 9:18 Comment(1)

If you have Xcode installed, you do not need the separate command line tools install. Just make sure you run xcode-select --switch /Applications/Xcode.app/Contents/Developer or xcode-select --reset so Terminal will use the command line tools inside Xcode instead of the ones installed by the "command line tools" standalone installer. From then on, the App Store will auto-update Xcode and your tools will stay current. – Sclerite 15/2, 2020 at 10:53

J

43

Mac OS : Big Sur

First Priority

sudo xcode-select --reset

sudo xcodebuild -license

Second Priority

xcode-select --install

Jilly answered 20/11, 2020 at 17:11 Comment(9)

Best answer for Big Sur – Laurinda 7/12, 2020 at 12:46

For big Sur, this first priority is usefull. Thanks for saving lot of time and Data. – Probationer 14/12, 2020 at 9:15

I am using Big Sur (xcode-select --install) helped me. – Stew 15/12, 2020 at 7:0

Work for me on catalina – Mcandrew 4/3, 2021 at 13:6

best answer! This issue doesn’t require installation of the tool again – Portecochere 31/3, 2021 at 16:36

According to the XCode man pages(Yea they do have documentation!!!) ``` -r, --reset Unsets any user-specified developer directory, so that the developer directory will be found via the default search mecha- nism. This command must be run with superuser permissions (see sudo(8)), and will affect all users on the system. ``` – Trantham 12/5, 2021 at 14:50

Thanks - worked for me! Why do MacOS upgrades always break dev tools? Disincentivizes upgrading since this is my dev laptop. – Rondi 6/7, 2021 at 22:4

Getting below error on BigSur ➜ ~ sudo xcodebuild -license dyld: dyld cache load error: existing shared cache in memory is not compatible dyld: Library not loaded: /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation Referenced from: /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild Reason: image not found xcrun: error: unable to locate xcodebuild, please make sure the path to the Xcode folder is set correctly! xcrun: error: You can set the path to the Xcode folder using /usr/bin/xcode-select -switch – Hives 27/8, 2021 at 7:37

R

35

Following worked on M1

ProductName:    macOS
ProductVersion: 11.2.1
BuildVersion:   20D74

% xcode-select --install

Agree the Terms and Conditions prompt, it will return following message on success.

% xcode-select: note: install requested for command line developer tools

Renitarenitent answered 13/2, 2021 at 18:55 Comment(0)

L

33

If you have Xcode downloaded manually (i.e. not from the App Store) or don't have Xcode at all:

sudo rm -rf /Library/Developer/CommandLineTools
Go to https://developer.apple.com/download/more/ to download Command Line Tools (macOS 10.14) for Xcode 10
Setup Command Line Tools

If you have Xcode installed from the App Store:

xcode-select --install

Lightheaded answered 5/11, 2018 at 9:2 Comment(3)

I want to install Command Line Tools only and Not Xcode. This solution seems to be the best. Minimal install – July 18/7, 2019 at 17:34

Perfect for me since I don't need Xcode but I do need Git :) – Cheerless 22/1, 2020 at 12:37

After I installed Catalina and trying the xcode-select --install answer I had an error from the UI installer: "xcode-select: note: install requested for command line developer tools". This was the only thing that worked for me since I didn't want to install Xcode. (I used the Command Line Tools for XCode 12.) – Angelesangelfish 27/9, 2020 at 21:11

A

30

Open Terminal:

install XCode developer tools and fix the problem.

$ xcode-select --install

Reset the path to Xcode if you have several versions:

$ xcode-select --switch /Applications/Xcode.app
$ xcode-select --switch /Library/Developer/CommandLineTools

Alcoholize answered 10/10, 2019 at 6:9 Comment(2)

If you have Xcode installed, you do not need the separate command line tools install. Just make sure you run xcode-select --switch /Applications/Xcode.app/Contents/Developer or xcode-select --reset so Terminal will use the command line tools inside Xcode instead of the ones installed by the "command line tools" standalone installer. From then on, the App Store will auto-update Xcode and your tools will stay current. – Sclerite 15/2, 2020 at 10:56

Also, it makes no sense to do both calls to xcode-select --switch above. The second one overwrites what the first one did. Do the first one and your command line tools will update as part of Xcode. – Sclerite 15/2, 2020 at 10:57

O

27

Run this command:

xcode-select --install

Hit return for a progress indicator on the Command Line Tools download.
After installation of the Command Line Tools has been completed, your Mac should be rebooted. If you’re getting “xcrun error invalid active developer path” while working in Terminal, refresh the application or relaunch it.

Even after following the above-mentioned steps, if you see the error: invalid active developer path (/Library/Developer/CommandLineTools). The next step would be to try and install Command Line Tools using a DMG file that can be downloaded directly from the Apple website.

Again, if you are using Homebrew, you need to update it. You don’t need to uninstall and again install Homebrew on Mac.

NOTE: If you are using Homebrew, try updating it after re-installing Command Line tools.

Credits: Git not working after macOS Update

Osmic answered 6/9, 2021 at 11:55 Comment(0)

I

14

This just happened to me after upgrading my MacBook Pro to macOS v13 (Ventura). After the upgrade, the Git command line stopped working with showing up this message.

xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun

Running brew upgrade fixed the Git command line.

Insightful answered 3/11, 2022 at 14:22 Comment(2)

Thank you, it worked. I've deleted Xcode before because I don't need it anymore. – Benefactor 3/11, 2022 at 15:59

I've got an error: Error: No developer tools installed – Cecilycecity 3/11, 2022 at 18:40

P

12

As of September 13, 2022, I had a similar issue after upgrading my MacBook Pro M1 to macOS v12.6 (Monterey), and although I followed some of the answers, my Mac kept prompting me with a dialogue to install Git as a developer tool. Every time that the installation was completed, I was prompted to the same dialogue.

Finally, I had to do a combination of all the answers to make it work:

First remove the command line tool:

sudo rm -rf /Library/Developer/CommandLineTools

Reinstall the xcode-select:
```
xcode-select --install
```

The above will prompt you with a dialogue to confirm the installation.

Set path to the Xcode folder with following:

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

Pandarus answered 13/9, 2022 at 19:24 Comment(0)

S

10

I observed in the Catalina privacy setting if Xcode not added in Full access disk I will get the same error, Xcode does not run scripts. Add your Xcode the same as in the attached image. After that clean build and run. Hope so it will work.

Sect answered 7/1, 2020 at 3:56 Comment(0)

D

9

For me, I didn't have xcode installed (on Mojave OS). I went to the App Store on my mac and downloaded it, then went back to terminal and typed git and hit enter, then it worked.

Dibbrun answered 31/10, 2018 at 21:46 Comment(0)

H

9

I found that my version of Xcode was too outdated and installing command-line-tools wasn't helping. Here's what I did:

I completely uninstalled the outdated XCode
I reinstalled the most recent XCode from the app store
That was all. Git was restored.

Hazy answered 22/1, 2019 at 21:52 Comment(0)

A

9

For me, for the macOS v13 (Ventura) user, installing this software helped:

I wasn't able to run any Xcode install commands, and Git was not working at all.

You can find this package here https://developer.apple.com/download/all/

Algia answered 17/10, 2022 at 15:25 Comment(1)

This also worked for me by installing Xcode through the App Store. – Alfreda 30/11, 2022 at 9:1

E

8

This works for me

sudo xcode-select --reset 
sudo xcodebuild -license

X-code must be installed.

Especially answered 4/3, 2019 at 14:32 Comment(0)

M

6

For those using Catalina and Xcode-beta:

sudo xcode-select -s /Applications/Xcode-beta.app/Contents/Developer

Marilumarilyn answered 14/8, 2019 at 3:22 Comment(0)

I

5

I updated my macOS yesterday，from macOS Mojave（10.14.6）to macOS Catalina（10.15.7），I was executing "git" command in my project. I get same errors。

run：

xcode-select --install

Irbm answered 11/8, 2021 at 1:0 Comment(1)

Please don't repeat existing answers – Silkweed 28/8, 2021 at 12:39

V

5

After Updating macOS to Monterey (12.3) from BigSur getting such issue

only worked-

xcode-select --install

Done!

Vanny answered 27/4, 2022 at 10:38 Comment(1)

That is the same with the accepted answer, but with less information! – Indite 28/4, 2022 at 8:41

T

5

With previous app development experience, may I say with confidence that the Git version delivered with Apple always create problems. So the sooner you get rid of Apple Git the better, so may I suggest:

brew uninstall git
brew update
brew install git

# which git
/usr/local/bin/git

Troika answered 14/9, 2022 at 11:30 Comment(1)

I think you might have the right idea bud. I ran into issues twice. Idk why I need a full development suite just to have git. – Dedie 15/9, 2022 at 0:4

F

4

For me It happened after Mac OS update to Mojave and git was not functioning in Intellij

Solution:- Go to Settings, then File | Settings | Version Control | Git and edit Path to Git executable field which is /usr/local/bin/git

Frankel answered 27/9, 2019 at 8:37 Comment(0)

E

4

I had the same issue and couldn't use SVN after the update,

Just in case if doing xcode-select --install didn't fix the issue,

You might see,

svn: error: The subversion command line tools are no longer provided by Xcode.

Refer : https://developer.apple.com/documentation/macos_release_notes/macos_catalina_10_15_release_notes

Try installing the svn by brew

brew install svn

This should get you going.

Enwind answered 12/6, 2020 at 15:10 Comment(1)

I have been thinking that brew is perhaps a better source for git! So much overhead using apple developer. – Dedie 5/12, 2022 at 15:24

C

3

MacOS :Monterey
Year: 2022

Solution: Upgrade to 12.2.1 or later

I upgraded to Monetery 12.2 as my Macbook pro got replaced. Ran into same issue as OP:

Git is not working after macOS Update (Xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools)

One would think that by this time Apple would have added xCode & developer tools into OS main build. Turned out they did. I had to upgrade to 12.2.1, which included "command line tools for xCode".
I still need to do step upgrade to 12.4 , but I believe we finally have these tools as part of OS build.

Here's screen-shot while attempting to upgrade from 12.2.1 to 12.3.1 (I forgot to take one while upgrading from 12.2 to 12.2.1, but I am pretty sure it had same Addons)

Crural answered 20/5, 2022 at 17:46 Comment(0)

U

3

I am using macOS v13 13.3.1 (Ventura) and an Intel chip MacBook Pro and ran this code:

xcode-select --install

This code worked for me from iTerm2, but I had to run the code twice and go through the installation twice.

It was a good option for me as it avoided installing all of Xcode and just the command line tools.

It took about 5 minutes with the crappy coffee shop Wi-Fi!

Unpracticed answered 9/5, 2023 at 20:13 Comment(0)

B

2

None of the above answers worked for me. I had a couple of issues. First, I installed the latest version of Xcode, 14.0 beta. That ended up not working because it was a version that is not compatible with Monterey. And my computer is too old to install Ventura beta. So I had to go and find out which version of Xcode actually did work. And that ended up being 13.4.1. So I installed that. I had taken all the right steps beforehand to delete the old version, and then placed the new one, as always, into my Applications folder. But for whatever reason, it did not end up there. When I checked to see if my install was successful, errors were thrown in Terminal. I had also previously updated CLT, which included the correct version. However, Terminal returned that I needed to install CLT. And when I tried, it told me that it was already installed, but I should change the path of my Xcode or install CLT (which obviously was not a real option). I found the solution in this article entitled Xcode-select active developer directory error. And I ran the following command in Terminal which fixed my path:

sudo xcode-select -s /Applications/Xcode.app/Contents/Developer

Hope this helps anyone else who encounters the same issue when trying to update Xcode on macOS Monterey and also can't update to macOS Ventura.

Blacksmith answered 13/7, 2022 at 22:37 Comment(1)

Identical to many of the existing answers. – Rhabdomancy 13/7, 2022 at 22:41

B

2

For macOS v13.0.1 (Ventura).

Update for macOS Ventura 13.0.1 (Nov 2022)

Install Command Line Tools for Xcode 14.1

It's worked for me.

Baronetage answered 30/11, 2022 at 6:26 Comment(2)

Came here after installing Ventura caused this issue. This worked for me too – Queeniequeenly 2/12, 2022 at 19:41

You should not just link to solutions. You can provide the link as reference but you should actually explicitly include the solution in your answer on Stackoverflow. – Ostracize 3/12, 2022 at 16:15

B

1

If you created a new Applications folder in an external drive and installed Xcode there:

sudo xcode-select --switch /Volumes/MyExternalStorageName/Applications/Xcode.app/Contents/Developer

Bear answered 26/10, 2020 at 20:17 Comment(0)

T

1

Edge case, but still worth writing down: when migrating from and older Mac with Migration Assistant, you may have selected the option to transfer all your applications from your older Mac. Applications, like Xcode needs to be updated if it was transferred and preserved OR delete from your other user's Applications folder. This is because Xcode has not been set up properly after the first start with the new OS version.

Travail answered 25/5, 2021 at 17:33 Comment(0)

N

1

I had this same issue after updating to macOS v13 (Ventura).

Command: xcode-select also does not seem to work. So does sudo xcodebuild.

After checking Xcode itself, it installs the command line tools and the said command still fails to work.

After checking this part, it appears to be blank. I just manually set it to use the available command line from the installed Xcode and everything now works, including Git.

Nadia answered 26/10, 2022 at 2:37 Comment(1)

related stuff. #17981259 so it is probably the order I did things that failed the commands. – Nadia 26/10, 2022 at 2:38

T

1

For macOS v13.1 (Ventura)

I updated from macOS v11 (Big Sur) to Ventura 13.1 (January 2023). I only installed Xcode on the App Store, and it worked for me.

Turman answered 20/1, 2023 at 0:7 Comment(3)

For me, I go to App store, update Xcode then have to do one more step, which is open Xcode and click to Agree with their license then everything is working fine. – Bernie 25/1, 2023 at 2:20

Yes, you have to open XCode so it can install the extra stuff that apparently includes git – Barratry 1/2, 2023 at 4:16

apple is really a data eater – Jarredjarrell 19/7, 2023 at 10:6

R

1

Answer for macOS v13 (Ventura)

Update the Xcode from App Store, and then run:

sudo xcode-select --reset

Explanation

First, updated the Xcode from App Store.

Make sure it is pointing to the correct location. Go to Xcode → Settings → Locations:

Then check the path of "active developer director". To check, run:

xcode-select -p

Output:

/Library/Developer/CommandLineTools

It is pointing to separately installed command line tools, which is incorrect, because we already have Xcode installed. It should point to the Applications folder where Xcode is installed. To do that, run:

sudo xcode-select --reset

Now it must have reset the path. Confirm it by running:

xcode-select -p

Output:

/Applications/Xcode.app/Contents/Developer

Just in case the reset doesn't fix the issue. Explicitly set the path:

sudo xcode-select -s /Applications/Xcode.app/Contents/Developer

Rhodia answered 5/8, 2023 at 22:26 Comment(0)

W

0

I had this problem in Mac Sonoma 14.3.1 and I fixed it with

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

hope it works for people that looking for this problem in Mac Sonoma

Wolffish answered 24/2 at 21:6 Comment(0)

A

0

I was able to fix this issue by downloading and installing Xcode from the Apple App Store.

specifications of this computer

chip: Apple M3 Pro

macOS: Sonoma 

version: 14.1

Asylum answered 8/4 at 5:29 Comment(0)

P

-1

After updating the Mac OS to Sonoma, I was facing the same issue. The below command helped me to resolve the issue

xcode-select --install

After running this command, you will be prompted to install, just click yes and continue with the installation.

Paolapaolina answered 6/3 at 7:56 Comment(0)

For macOS v13.1 (Ventura)

Answer for macOS v13 (Ventura)

Explanation

Recommended topics

Hot tags