The best way to fix Xcode is to download and install Xcode yourself rather than relying on the App Store or automatic updates. If that doesn’t fix the issue, restart and try a reset: xcode-select -reset Xcode To fix Xcode command-line tools, also known as xcode-select, but not Xcode - it’s confusing I know - try this command: xcode-select -install If you’re just using the Xcode command-line tools (less than 200 MB) versus full Xcode (about 16 gigabytes when extracted), you can save a lot of download time.
Xcode Command-Line Tools (not full Xcode) You can check by going to Finder, then Applications, and look for “Xcode.app.” If you see that, you’re using full Xcode. The type of Xcode fix you’ll need depends on the answer to one big question: do you use full Xcode? Most developers will probably have the whole enchilada. When I tried to run a tool that relies on Xcode, the Mac gave this xcrun error: xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun. Most of the time, my Mac simply reported failure: Unable to Install Update. Once it reported it could not download Xcode: Unable to Download App. The App Store kept trying to update Xcode each night through automatic updates. With the Catalina upgrade, my Xcode did not automatically update to 11.1.
While these issues will mostly affect developers, the fixes might help others as well. Many developer tools on Macs rely on Xcode behind the scenes. If you use Xcode, I recommend fixing Xcode first. Errors and problemsĪfter upgrading to Catalina, I’ve run into three types of issues: Xcode, Homebrew, and Ruby/Gems-related. Setting up your Mac for development for the first time? See my article Zero to Hero: Set Up Your Mac for Software Development.
0 kommentar(er)
