Still seeing xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools)? If you are using Homebrew, you should also be sure to update Homebrew after you have (re)installed Command Line Tools.

Once the installation of Command Line Tools has completed, you should reboot the Mac (sometimes simply refreshing, relaunching Terminal, or opening a new Terminal may resolve the ‘xcrun error invalid active developer path’ message too, but a reboot is recommended). Hitting return will cause a pop-up to appear with a progress indicator on the download for Command Line Tools. Installing/reinstalling CLT can be done from the command line by issuing the following command string in Terminal: Yes, even if you already have command line tools installed, you should reinstall it to resolve the error message, particularly if you are only experiencing the error after a system software update (eg, from Mojave to Monterey).

The solution, as you may have guessed from the error message itself, is to reinstall or install Command Line Tools.

Xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun Fix “xcrun: error: invalid active developer path” Error in Terminal on MacOS

Fortunately it’s easy to fix the “xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools)” error message, and get git, pip, Homebrew, or whatever other command line tool that failed, to start working again.įor what it’s worth, the full error message is:

Install git for mac os x