Xcode Not Installing


Click again to start watching. This process was working using Xcode 12, and now fails with xcodebuild after installing Xcode 13. I am using the xcodebuild -exportArchive command to package the.ipa, however it now reports the following: 2021-10-04 07: 54: 28.248 xcodebuild 53863: 11183390 MT IDEDistribution: - IDEDistributionLogging. Homebrew is now working great with just the command line tools and I have 9 GB back! Therefore, if you have removed Xcode from your system and just installed the command line tools, you will have to manually run the above command line. 3: If you are not able to install the XCode CLI using terminal command. Sudo xcode-select -install. Question or issue on macOS: I’m using the Mac OS to install the XCode10.1. I have 18.43GB free disk space in the mac, but when I click the install button on the Xcode from the app store, it’s always show the “Not enough storage disk space, you can’t install the product” alert message.

  1. Here’s how you can download and install via the Mac App Store: Make sure you’re logged into macOS with your Apple ID. Open the Mac App Store app. Search for “xcode” in the search field, at the top-left. Click on the Xcode app item that appears. Click on the Get or Install buttom at the top-right to download and install Xcode.
  2. In this case, uninstalling the package and installing from sources is the recommended way to go. We offer packages for a number of Linux distributions in 64 bit thanks to PackageCloud.io so you can use your distro's package manager to install and keep Aircrack-ng up to date.

After the MacOS 10.14.4 Update, softwareupdate also shows me the following as a further update/ download: Command Line Tools (macOS Mojave version 10.14) for Xcode 10.2. Now if I need it, I am fine installing it. I am wondering why I need it though, since I don't have Xcode installed, and am not developing software in any sense.

Updating your MacBook or iMac should be free of headaches and drama. Apple even coined a marketing phrase “it just works!” But recently, a lot of readers and Mac users are finding the opposite–it just doesn’t work! Several users have recently had issues updating their MacBook with the latest version of macOS. Unfortunately, this appears to be a fairly common problem for some when updating to the latest macOS High Sierra update.

The update gets stuck with a message “mac os could not be installed on your computer an error occurred installing macOS.” Some folks report seeing this message as well “the path /System/Installation/Packages/OSInstall.mpkg appears to be missing or damaged.”

Then your Mac prompts you to quit the installer and restart your computer. Well, Apple, whatever happened to it just works???


  • 1 Quick Tips
  • 2 Getting macOS could not be installed on your computer?
  • 3 How-To Fix macOS could not be installed issue
  • 6 Reader Tips

Quick Tips

  • Check that your Mac’s Date&Time are on Set Automatically
  • Reset your Mac’s NVRAM or PRAM
  • Free up some internal hard drive storage
  • Restart in Safe Mode and run Disk Utility’s First Aid
  • Try Recovery Mode
  • Use Terminal to identify and remove non-Apple KEXTs
  • Restart in Single User Mode to remove problematic files


Getting macOS could not be installed on your computer?

If you are experiencing this issue with your update, here are a few tips that you can use to address this issue. Before proceeding with the steps below, we suggest that you ensure your Mac’s clock is correct. If your Mac’s Date&Time do not match your current timezone or date, macOS often won’t install. Go to System Preferences > Date & Time. Apple prefers if you choose the option to Set Automatically.

Next, let’s try out the basic NVRAM reset (or PRAM for older Macs) on your computer.

Follow these steps if you are not sure about how to do the NVRAM reset

  1. Shut down your Mac
  2. Turn it on and immediately press and hold these four keys together: Option, Command, P, and R
  3. Release the keys after about 20 seconds, during which your Mac might appear to restart
  4. Open System Preferences and check (and adjust, if necessary) any settings that reset, like volume, display resolution, startup disk selection, or time zone

Check Storage

The other thing is to make sure that your MacBook/Mac has enough space available to complete the update. If you are running low on space, Apple provides some guidelines that can help you recover some space on your Mac.

Beyond the Basics

Now, that we have taken care of the basics, we suggest that you try each of the processes below until your macOS install problem is fixed. We arranged the how-to-fix steps in three separate categories.

The first of the troubleshooting steps walk you through Safe mode options and then we suggest the Recovery mode. The last of the options shows you how to remove third-party KEXT files using simple terminal commands and then try the install process.

How-To Fix macOS could not be installed issue

Fixing the Install issue using Safe Mode on your Macbook

  • One of the best practices around updating is to make sure that you have taken a backup of the system before doing any troubleshooting. Better Safe than Sorry. We are assuming that you have already backed up your machine before you proceed with any of the steps below
  • The first thing to try is to get your Mac/MacBook into Safe mode. When you hold the ‘Shift’ key during startup, your computer will launch into Safe mode
  • Safe mode essentially forces the initiated process to ignore all third party launch daemons and startup items. Once you are in the Safe mode, the next course of action is to get into Disk Utility. Once your MacBook has entered safe mode, you will see it indicated in the top right-hand corner of your screen
  • Log in using your credentials and then go to your macOS Utilities folder. Here you will need to start up the Disk Utility Program. Once in the program, Click First Aid on the top and choose the volume (Your main HDD) and start the repair process
  • Once the Repair has completed, you will be notified of the status. At this point, you would want to rerun the macOS Update program and see if it works for you without giving you the error message

If you tried the steps above in Safe mode and did not find success, the next course of action is to try the Recovery mode.

Fixing macOS Install Problem in Recovery Mode

  • To get to recovery mode on your Mac or MacBook, you will need to press and hold Command + R keys together when booting up your computer
  • Once you are in the Recovery mode, click on the Apple logo on the top left corner of the screen and make sure that your startup disk is pointing to the Mac Boot disk
  • Now find the macOS update program and run the update

Sometimes, when you are facing install/upgrade issues, a workaround that works for many users is to create an external bootable installer and try to run the install program using it. Apple provides a detailed white paper on this process. You can create the bootable installer on a USB and then try it to update the macOS.

Removing Third Party KEXT Files

If you are still reading and have already tried the series of fixes in both Safe mode and Recovery mode to no avail, you may have to roll up your sleeves and do a little more digging into the root cause of the issue. Sometimes it’s the third party KEXT extensions that cause a lot of heartache during update/install of macOS.

These KEXT Files get added to your Mac/MacBook when you are using third-party devices. If you are not sure about it, your best bet is to look and see what third-party extensions are currently there on your machine.

To do so, Open up terminal from your utilities and type in the following to see the non-Apple KEXTs.

Kextstat grep –v com.apple

This command should show you all the third party extensions. Now you can remove them one by one or remove the one that you think may be the suspect. Using terminal, you can unload the kext my using the following command.

sudo kextunload /System/Library/Extensions/NAMEOFTHEKEXT.kext

Here ‘NAMEOFTHEKEXT’ needs to be replaced with the appropriate suspect KEXT file that you found above. Once you have unloaded the KEXT, you can go back and check to make sure that it has indeed been removed by using the kextstat command.

Once you have removed all the third party KEXT files and have made sure that you have enough space on your machine for the macOS update, please try and relaunch the install process.

Problems? Try Single User Mode

If your install process is failing because of a particular problematic file, you can also try to log in using the single user mode and delete that specific file and then try resuming the install. Sometimes you find these problematic ones off files in the Installer log files. To access these log files, open up the Console app in utilities and click on ‘/var/log’ on the left-hand column and then choose ‘instal.log’in the next column.

We are hoping that you were able to fix the macOS Install issue using some of these tips. If you have tried everything without any success, your best bet is to reach out to Apple Support folks so that they can help out. Please let us know how your install worked by using the comments below.

Reader Tips

  • Try restarting in recovery mode and install macOS High Sierra or Sierra from a bootable USB drive disk. If necessary, reformat your SSD to Mac OS Extended (Journaled), not APFS
  • Try setting up another admin user account to see if the same problem continues
  • Boot up your Mac using Cmd + R to access the recovery partition. Immediately, go the Apple menu choose Startup Disk. Select your HD. Unlocked it if necessary by entering your admin password. Reboot and see if it starts up normally
  • Update your system’s clock by using Terminal. Open Applications > Utilities >Terminal and type the command date. If the date listed is incorrect, type this command ntpdate -u “time.apple.com” then press return. If you live outside of the Americas, type in Apple’s time server nearest you, such as time.asia.apple.com or time.euro.apple.com inside the parenthesis
  • I created an ISO image of macOS High Sierra on a USB and installation was a breeze after that
  • Shut down your Mac and wait 30 seconds. After 30 seconds, press the power button and immediately hold down Command + R and keep pressing these keys until the apple logo appears. You should see a screen asking you to choose a language, select your language of choice, and navigate to your macOS Utilities. Check the WiFi button at the top right to make sure you’re connected to the internet. Then select reinstall the latest version of macOS, click continue, agree and allow it to download and restart on its own (just leave the Mac alone–really!) After macOS reinstalls, it should restart and end up at the login screen
  • I booted up while holding the Option key and chose my regular MacinstoshHD (not an update volume). Then I booted normally (not with safe mode) and tried again to reinstall the update. Took several reboots but in the end, it worked!
  • Oftentimes, this error means your Mac is trying to boot from a different HD partition, sometimes even the recovery partition. To fix it, restart in startup manager (holding option key) and select your regular HD to reboot from. Once successful, go to System Preferences > Startup Disk > Select your normal HD startup. That should fix the problem

Obsessed with tech since the early arrival of A/UX on Apple, Sudz (SK) is responsible for the editorial direction of AppleToolBox. He is based out of Los Angeles, CA.

Sudz specializes in covering all things macOS, having reviewed dozens of OS X and macOS developments over the years.

In a former life, Sudz worked helping Fortune 100 companies with their technology and business transformation aspirations.

Xcode Not Installing

Today Apple released macOS Big Sur 11.0 -10.16 (20A4299v) Beta 1 to Developers.

UPDATE 6/23/20 – Keep an eye on my Big Sur Need to Know changes article. I will be constantly updating it as new info comes in. mrmacintosh.com/macos-big-sur-11-0-updated-index-of-need-to-know-changes-links/

MacOS Big Sur 11.0 -10.16 (20A4299v) Beta 1 was released today on June 22nd, 2020 at 2:00 CST right after the keynote.

Update Xcode Windows

macOS Big Sur 11.0 Patch Notes

Just like last year, the 11.0 beta 1 patch notes list is huge! The amount of detail is just what MacAdmins are looking for! Let me give you some stats from the 11.0 Beta 1 Patch notes document.

  • 1 Important Known Issue
  • 4 Deprecations
  • 11 New Features
  • 1 Resolved issues
  • 60 Known Issues – Core OS, Apps, Xcode & SwiftUI

Public Link (non developer) = developer.apple.com/documentation/macos-release-notes/macos-big-sur-11-beta-release-notes

MacAdmin Patch Notes of Interest

  • Updating to macOS Big Sur 11 beta from previous versions of macOS might take significantly longer than expected. Data loss could occur if the update is interrupted. (59101197)
  • If macOS Big Sur 11 beta is installed into the same APFS container as previous versions of macOS, system software updates can no longer be installed on the previous versions of macOS. (64411484)
  • Installing a new kernel extension requires signing in as an Admin user. During kernel extension development, every time a kernel extension is changed, it must be signed and notarized. In both cases, your Mac must be restarted to load the extension. (55068348)
  • If you updated to macOS Big Sur 11 beta from a previous version of macOS, Software Update might show “Unable to check for updates – Failed to download the documentation for the minor update. Please try again later”. (63158434)Workaround Below
  • Kernel extensions using certain deprecated KPIs no longer load. Refer to the support page. While macOS Big Sur remains in development, you can temporarily disable System Integrity Protection to allow these deprecated extensions to load. (55068348)
  • macOS Big Sur 11 beta improves system security by requiring an administrator password when a certificate trust settings change is made in the admin trust domain. Running as the root user alone is no longer sufficient to modify certificate trust. User trust domain settings continue to require confirmation by entering the password for the user’s account.

macOS Big Sur 11.0 Installer Info

Full Installer.app

Link – developer.apple.com

Xcode Not Installing On Catalina

Size = 9.57GB

Product ID = 001-18401-003

Requirements – ?

T2 BridgeOS Update

T2 BridgeOS was updated along with the 11.0 upgrade

Size = 440.1 MB

Product ID = 001-18400

BridgeOS Update Version = 18.16.10310.5.15

New Software Update Catalog URL


Report bugs NOW!

Now that macOS Big Sur 11.0 Beta is live, start testing as soon as you can! You will want to submit any bugs that you find into Apple ASAP. If you get bugs in quickly, they could be fixed in the current beta cycle instead of waiting until after the public release. If not, you could be waiting months before the fix is put into a dot release combo update.

macOS Big Sur 11.0 (20A4299v) Beta 1 Release Notes

I always post the full patch notes to this page to document them for you. The reason behind that is that Apple will usually just replace over the old patch notes so you are then unable to see what was fixed in the previous release.


The macOS 11 SDK provides support to develop apps for Macs running macOS Big Sur 11. The SDK comes bundled with Xcode 12 beta. For information on the compatibility requirements for Xcode 12 beta, see Xcode 12 Beta Release Notes.


Xcode Update Won't Install

Known Issues


Updating to macOS Big Sur 11 beta from previous versions of macOS might take significantly longer than expected. Data loss could occur if the update is interrupted. (59101197)

Third-Party Apps

Known Issues

  • CMake might not run, install, or might generate invalid outputs. (62905973)Workaround: Update to CMake 3.18rc1.


Known Issues

  • VoiceOver might be unavailable at certain times while installing macOS Big Sur 11 beta. (63025357)

App Store

New Features

  • SKStoreProductViewController and SKProductStorePromotionController APIs are now available for both macOS and Mac Catalyst apps. (56300909)


  • See AppKit Release Notes for macOS Big Sur 11.

Auto Unlock

Known Issues

  • You might be unable to set up Auto Unlock. (64120075)


Known Issues

  • If you click the Directions button on a calendar notification, Maps might not launch as expected. (63697152)
  • It isn’t possible to edit Calendar widgets. (63984003)
  • Accounts might not be visible in Preferences. (64117985)


Known Issues

  • Continuity Handoff isn’t currently available in macOS Big Sur 11 beta. (64140413)

Core ML

Known Issues

  • When setting isSynchronizationEnabled to true on a MLModelCollection, the initial download may take longer than expected to complete. The collection then becomes available. (64131243)


  • The default initializer on the auto-generated model interface has been deprecated in favor of init(configuration:). Please use init(configuration:) or the newly introduced .load() method and handle model load errors as appropriate. (64432588)

Desktop Picture

Known Issues

  • If the desktop picture was never changed from the default macOS Catalina 10.15 image, it will persist after updating to macOS Big Sur 11 beta, even though the new default desktop picture is displayed in Desktop and Screen Saver preferences. (64390185)

Installer and Software Update

Known Issues

  • If you updated to macOS Big Sur 11 beta from a previous version of macOS, Software Update might show “Unable to check for updates – Failed to download the documentation for the minor update. Please try again later”. (63158434)Workaround:
    1. Start up from macOS Recovery.
    2. If your data volume is encrypted, use Disk Utility to mount it.
    3. In Terminal type rm -rf '/Volumes/Macintosh HD - Data/private/var/folders/zz/zyxvpxvq6csfxvn_n00000y800007k'.
    4. Restart your Mac.
  • You might need to adjust Energy Saver settings so your Mac doesn’t go to sleep while preparing to install macOS Big Sur 11 beta. (63166401)
  • APFS containers with non-default allocation block sizes aren’t currently supported for installation. (64312561)
  • Update iMac Pro to macOS High Sierra 10.13.6 or later before installing macOS Big Sur 11 beta. (64314272)
  • Installation might pause on Macs that don’t have input devices connected. (64348347)Workaround: Connect an input device and dismiss the alerts to continue installation.
  • You might be unable to install macOS Big Sur 11 beta onto additional volumes. (63677460, 64445236)Workaround: Create a bootable installer using the createinstallmedia command.
  • Software Update might unexpectedly indicate updates for your Mac are being managed by swscan.apple.com, instead of indicating your Mac is enrolled in the Apple Beta Software Program. This doesn’t impact your ability to update macOS Big Sur 11 beta. (64407436)
  • If macOS Big Sur 11 beta is installed into the same APFS container as previous versions of macOS, system software updates can no longer be installed on the previous versions of macOS. (64411484)
  • Installation on Core Storage Fusion volumes with FileVault encryption enabled isn’t currently supported. (64472080)


New Features

  • The kern.argmax limit has been increased, allowing programs to receive longer argument lists. (48661669)
  • Darwin kevent now allows non-parent processes to register for NOTE_EXITSTATUS, which delivers the same values as the wait() family of functions in the event data. Refer to the wait4() man page for more information. This event is subject to the following security checks:
    • The requesting process is allowed to send signals by sandbox restrictions.
    • The requesting process and the target process are running as the same user or the requesting process has root privileges. (58134463)

Known Issues

  • Installing a new kernel extension requires signing in as an Admin user. During kernel extension development, every time a kernel extension is changed, it must be signed and notarized. In both cases, your Mac must be restarted to load the extension. (55068348)
  • Remote panic dumps aren’t currently available. (57915324)
  • New in macOS Big Sur 11 beta, the system ships with a built-in dynamic linker cache of all system-provided libraries. As part of this change, copies of dynamic libraries are no longer present on the filesystem. Code that attempts to check for dynamic library presence by looking for a file at a path or enumerating a directory will fail. Instead, check for library presence by attempting to dlopen() the path, which will correctly check for the library in the cache. (62986286)
  • kmutil install might fail to build a development kextcache. (63772702)Workaround: Copy the release .elides to the locations of the development .elides:sudo cp /path/to/livemount/System/Library/KernelCollections/BootKernelExtensions.kc.elides /path/to/livemount/System/Library/KernelCollections/BootKernelExtensions.kc.development.elidessudo cp /path/to/livemount/System/Library/KernelCollections/BootKernelExtensions.kc.elides /path/to/livemount/System/Library/KernelCollections/BootKernelExtensions.kc.kasan.elides sudo cp /path/to/livemount/System/Library/KernelCollections/BootKernelExtensions.kc.elides /path/to/livemount/System/Library/KernelCollections/BootKernelExtensions.kc.debug.elidessudo cp /path/to/livemount/System/Library/KernelCollections/SystemKernelExtensions.kc.elides /path/to/livemount/System/Library/KernelCollections/SystemKernelExtensions.kc.development.elidessudo cp /path/to/livemount/System/Library/KernelCollections/SystemKernelExtensions.kc.elides /path/to/livemount/System/Library/KernelCollections/SystemKernelExtensions.kc.kasan.elidessudo cp /path/to/livemount/System/Library/KernelCollections/SystemKernelExtensions.kc.elides /path/to/livemount/System/Library/KernelCollections/SystemKernelExtensions.kc.debug.elides
  • Use only absolute paths with the --volume-root option of kmutil, and don’t use a trailing /. (63773848)
  • After removing a DriverKit extension, restart your Mac to complete uninstallation. (63995046)
  • Adhoc signed kernel extensions are displayed with a developer name of unknown in update dialogs and in Security preferences. (64215260)
  • Symbols exported by both xnu and Apple kernel extensions will change. Recompile your kernel extension with each update to macOS Big Sur 11 beta to ensure compatibility. (64262563)
  • Moving a kernel extension bundle out of /Library/Extensions might not completely uninstall it. (64331929)Workaround:
    1. Remove the extension from /Library/Extensions.
    2. Boot to macOS Recovery.
    3. Run Terminal.
    4. Enter the command kmutil invoke-panic-medic.
    5. Restart your Mac.
    6. Follow the prompt to open System Preferences and navigate to Security & Privacy.
    7. Follow the prompt to restart.
  • An unexpected System Extension Updated alert for third-party kernel extensions which are included in macOS might appear. These include: Accusys, Inc., ATTO Technology, Inc., Areca Technology Corporation, CalDigit, Inc., HighPoint Technologies, Inc., Promise Technology Mobile Apps, and Other World Computing. (64337113)


  • Kernel extensions using certain deprecated KPIs no longer load. Refer to the support page. While macOS Big Sur remains in development, you can temporarily disable System Integrity Protection to allow these deprecated extensions to load. (55068348)


Known Issues

  • Certain languages might exhibit clipped or misaligned layout. (63105445)
  • Certain languages might display unlocalized text. (63105674, 64040564, 64045718)
  • Some keyboard shortcuts might not work when running macOS Big Sur 11 beta in a language other than English. (63834383)


Known Issues

  • Widgets have access to location information even if the NSWidgetWantsLocation key isn’t in their Info.plist. (61953645)
  • In Swift, the authorizationStatus() property of CLLocationManager is incorrectly exposed as a method instead of a property. (62853845)


New Features

  • New APIs are available for using os_log from Swift as part of the os framework:
    • A new type Logger can be instantiated using a subsystem and category and provides methods for logging at different levels (debug(_:), error(_:), fault(_:)).
    • The Logger APIs support specifying most formatting and privacy options supported by legacy os_log APIs.
    • The new APIs provide significant performance improvements over the legacy APIs.
    • You can now pass Swift string interpolation to the os_log function.
    Note: The new APIs can’t be back deployed; however, the existing os_log API remains available for back deployment. (22539144)

Macos Xcode Command Line Tools

Mac Catalyst

Known Issues

  • Content Extensions require a temporary workaround. (57442394)Workaround: Add the following key/value pair to the NSExtension dictionary in the Info.plist: 'NSExtensionContainingViewControllerClass' = '_UNNotificationContentExtensionViewController'.
  • The new PHPickerViewController API currently produces unexpected results. (63631906)


Known Issues

  • If Messages is launched immediately after logging into iCloud, a login window might be displayed unexpectedly. (56309057)Workaround: Relaunch Messages after a few minutes or try restarting your Mac.
  • You might be unable to type in the photo picker search field when attaching a photo. (60011306)Workaround: Click the search field, press the tab key, then click the search field again.
  • You might receive an alert that indicates the maximum number of pinned conversations has been reached. (62919406)Workaround: Pin the conversation using drag and drop instead of using a swipe action or quick action with Haptic Touch.
  • Keyboard navigation to move focus between controls isn’t currently available. (63987810)
  • Messages Preferences are inaccessible until at least one message has been sent or received. (64122975)
  • Autocomplete fields and conversation titles aren’t visible while Messages is in full-screen mode. (64134303)
  • Message outlines might be missing when printing or exporting a conversation as a PDF. (64181169)
  • The first and last name fields in Messages Preferences might be misaligned. (64346872)Workaround: Set up your name in Messages Preferences by following the placeholder text then close and reopen Messages Preferences.


Known Issues

  • The logs property isn’t currently available from Swift while using Shader Validation. (64055248)

Migration Assistant

Known Issues

  • You might need to reset the password for a Standard account after migration, if the previous password doesn’t work. (63878129)Workaround: Log into an Admin account and change the Standard account’s password in the Users & Groups system preference.


Known Issues

  • Many elements of the user interface are currently missing when running Motion on macOS Big Sur 11 beta. (62531765)


Known Issues

  • Music might quit unexpectedly while using the search field. (64183834)


New Features

  • Experimental HTTP/3 support can be enabled in Safari via Experimental Features in the Developer menu, and enabled system-wide using the Terminal command defaults write -g CFNetworkHTTP3Override -int 3. (62969220)

Known Issues

  • HTTP/3 Draft 29 isn’t yet supported. (63524866)

Phone and FaceTime

Known Issues

  • Regular and emergency Wi-Fi calling using iPadOS 14 beta, macOS Big Sur 11 beta, and watchOS 7 beta isn’t currently available for T-Mobile USA customers. (63078572)


Known Issues

Xcode Not Installing

  • Importing Quartz or PDFKit frameworks in the macOS SDK might result in an errors such as “Umbrella for module ‘Quartz.PDFKit’ already covers this directory”. (63886438)

Safari and Webkit

New Features

  • Support for Web Extensions is now available. Existing Chrome and Firefox extensions can be converted for Safari using xcrun safari-web-extension-converter and distributed through the App Store for use in Safari 14. (55707949)
  • Webpage Translation is now available in the U.S. and Canada. Supported languages include English, Spanish, Simplified Chinese, French, German, Russian, and Brazilian Portuguese. Safari will automatically detect if translation is available based on your Preferred Languages list. (64437861)

Known Issues

  • Safari might quit unexpectedly when opening the Start Page if Frequently Visited Sites are visible as thumbnails. (63945984)Workaround: Make the window wider, hide the sidebar, or Control-click on Frequently Visited Sites and choose View as Icons.


New Features

  • macOS Big Sur 11 beta improves system security by requiring an administrator password when a certificate trust settings change is made in the admin trust domain. Running as the root user alone is no longer sufficient to modify certificate trust. User trust domain settings continue to require confirmation by entering the password for the user’s account. This change may affect you if one of the following is true:
    • You have written scripts which call /usr/bin/security add-trusted-cert -d ... as root.
    • Your process runs as root and calls the SecTrustSettingsSetTrustSettings function to trust a certificate.
  • Workflows that add trust settings in the admin trust domain, such as for an enterprise root certificate, may require modification if the user can’t authenticate as an administrator at the time settings are changed. (21855995)Workaround: Use Apple Configurator 2 to create and install a configuration profile containing your root certificate.

Xcode Not Installing Windows 7


Xcode Not Installing

Known Issues

  • When quickly typing a search query in Spotlight, the result from a previous search might appear, then pressing return may create a wrong launch shortcut for subsequent queries. (64428836)Workaround: Type your query and click the desired result from the list that appears.
  • If you can’t find an application using Spotlight, launch the application at least once using Finder. (64463806)


Known Issues

  • Disclosure groups in Forms might produce unexpected results. (64079102)
  • Nested disclosure groups generated by OutlineGroup might produce unexpected results. (64097731)
  • The SceneStorage property wrapper isn’t yet supported. (64414712)
  • A label used with a symbol image might appear misaligned. (60193698)


Known Issues

  • Driver extensions might not launch on-demand after installation. (51229724)Workaround: Disable System Integrity Protection, then launch Terminal and execute the following command before approving the newly installed driver: sudo touch /Library/DriverExtensions.

Touch ID

Known Issues

Xcode Not Installing Pc

  • Touch ID might become unexpectedly disabled on Macs with a T2 Security Chip after installing multiple operating systems. (62608379)Workaround: Reset the SMC of your Mac.


New Features

  • hv_vcpu_run_until(_:_:) now supports the deadline HV_DEADLINE_FOREVER. (57025216)
  • The new hv_vcpu_enable_managed_msr(_:_:_:) and hv_vcpu_set_msr_access(_:_:_:) enable direct MSR access from a guest. (50291076)


  • The function hv_vcpu_run(_:) is deprecated.


Known Issues

  • The NSSecureCoding implementation of VNRecognizedPointsObservation currently causes initWithCoder: to fail. (63681919)

Installing Xcode On Mac

Xcode Not Installing On Android


  • The VNIdentifiedPointsObservation class is deprecated. Use VNRecognizedPointsObservation instances instead. (63690311)

Macos Xcode Install

Xcode Previews

Xcode Not Installing On Mac

Resolved Issues

  • Rebuilding against the iOS 14, macOS 11, watchOS 7, and tvOS 14 SDKs changes uses of GeometryReader to reliably top-leading align the views inside the GeometryReader. This was the previous behavior, except when it wasn’t possible to detect a single static view inside the GeometryReader. (59722992) (FB7597816)

Big Sur 11.0 Beta 1

Questions or issues ? Contact Me