Today Apple released macOS Big Sur Beta 9 (20A5384c) to Developers
MacOS Big Sur 11 Beta 9 (20A5384c) was released on September 29th, 2020 only one week after Beta 8! We are starting to get weekly beta releases. MacOS Catalina had 11 beta releases including the gold master, so again we are getting very close to release. Beta 7 & 8 did not get a full installer so hopefully we get one this time around. I’m still waiting to see if any changes are listed around screen recording, I will update as soon.
UPDATE: 10/05 – softwareupdate --fetch-full-installer does not work in Big Sur Beta 9
UPDATE: 9/30 – Apple has just released a Beta 9 Full Installer!!!
Released on 9/30 at 12PM CST a Beta 9 Full Installer!
UPDATE 9/29 – Items not found in Big Sur Beta 9 official patch notes
Beta 9 does not have a full installer available 🙁
We now control screen recording access for standard users with MDM! (More information available in the AppleSeed patch notes)
Active Directory login is still not working in Beta 9. Hopefully it’s fixed in the next release. The plugin was working fine in Beta 6 and 7.
Xcode command line tools are now available for 12.2 Beta 2
Setup assistant bug where you could not hit continue = Fixed.
Beta 9 seems to take longer to prepare the install (30min+)
2. 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)
Previous Big Sur 11 Beta Releases
9. Big Sur 11 Beta 9 (20A5384c) – 09/29/20 – Current Release
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 Beta 9 (20A5384c) Release Notes
Overview
The macOS 11 SDK provides support to develop apps for Macs running macOS Big Sur 11. The SDK comes bundled with Xcode 12.2 beta, available from Beta Software Downloads. For information on the compatibility requirements for Xcode 12.2, see Xcode 12.2 Beta Release Notes.
Catalina 10.15.7 Update = accountsd using 400% CPU if using iCloud
Catalina 10.15.7 Update is causing problems with the accountsd process. The issue only seems to happen if you use iCloud Drive, Mail, Calendar or Internet Accounts.
Something is wrong with the iCloud sync process. Users are saying that after they installed the 10.15.7 update, the accountsd process runs up to 400%+ in Activity Monitor. When the issue starts, it slows the Mac down to a crawl. This causes the Mac to quickly drain the battery, heat up and kick the CPU fans into high gear. Another process that could be acting up is suggestd.
UPDATE 9/29 10:00AM – I’ve added 2 new fixes in the workarounds section below. One kills the cm.apple.iCloudHelper process and recreates the .sqlite database. The other was to remove Find My Mac then re enable it.
This comes after I reported major problems with the macOS Mojave 2020-005 Security Update that came out on the same day. Apple has pulled both the Safari 14.0 and Mojave 2020-005 Security Updates.
If you use iCloud – Drive, Mail & Calander and you have installed the 10.15.7 update, you might have problems. Finder will be sluggish and general system speed is slow. If you open up Activity Monitor and then select the CPU tab, you might see accountsd taking up a huge amount of CPU. It might be running at over 400%, you can see what that looks like in the screenshot below.
accountsd taking up over 400% CPU
2. Affected macOS Build Versions
This issue affects the following macOS Build Versions.
macOS Catalina 10.15.7 Update(19H2) – Released on September 24th, 2020
macOS Catalina 10.15.6 and below, as I noticed a few reports from 10.15.6 around the 25th. For 10.15.6 users, sometimes just updating to 10.15.7 fixes the issue for them.
No reports so far of this happening on macOS Mojave 10.14 or High Sierra 10.13.
Looks like a variant of this issue goes all the way back to the Catalina 10.15.1 Update. But most reports disappeared until it came back after installing 10.15.7.
3. Affected Mac Hardware
Past problems would only happen with certain hardware models. Not this time, if you installed the Catalina 10.15.7 Update on a compatible Mac you might have problems. As I noted in the Affected macOS Build Versions above, the issue could be affecting 10.15.6 and below users.
4. What is the accountsd process?
From Apple
Help users access and manage their external accounts from within your app, without requiring them to enter login credentials. The Accounts framework provides access to user accounts stored in the Accounts database, which is managed by the system. An account stores the login credentials of a particular service, such as Twitter, and you use those credentials to authenticate with the service. When you integrate the Accounts framework into your app, you don’t need to store account logins yourself. Instead, the user grants your app access to use their account login credentials, bypassing the need to type their username and password. If no account for a particular service exists in the user’s Accounts database, you can let them create and save an account from within your app.
The first reports came in on Friday, one day after Apple released the Catalina 10.17.5 Update.
accountsd process is eating 500% cpu and making macbook pro 15,1 useless after Catalina 10.15.7 update. Even if you force this process to quit it comes back at ~500% CPU and make lots os apps to hang.
More reports started to roll in on the Apple Discussion Forums.
Same here, upgraded to 10.15.7 and CPU usage spikes. Seems that the processes ‘accountds’/ ‘commerce’ are responsible for this and killing the process ‘commerce’ is a only a temp ‘solution’ for minutes and then same problem appears again. Tried also SMC reset without success!!!
I just updated to Catalina last month. Everything was running smooth and fine under 10.15.6. I did the 10.15.7 update yesterday first through the normal way –> system preferences – Software update and then the trouble with the accountsd-process has also begun.
Additionally, boot time is slower, logging in is slower and when doing so I’m met with a blank desktop which needs 7-8 seconds before icons finally appear. Everything feels sluggish, and applications also take more than twice as long to start up.
After reading multiple reports I felt that it was time me to take a closer look.
6. I’m trying to replicate this issue now.
When issues like this have come up in the past, I might not be able to reproduce them. I have to go purely on user reports, which at times can be tough. I want to make sure the reporting is very accurate.
The test Mac was setup with the exact settings that most of the users have reported.
1. Install 10.15.6
2. Set Up iCloud Drive, Mail and Cal
3. Install 10.15.6 Update > 10.15.7
4. Test settings.
I’ve been unable to reproduce this issue. I had the article ready for this weekend but did not have enough solid reports of the issue. Now enough reports have come in to solidify the issue as a problem for users.
7. Workarounds / Fixes
This list of workarounds will start from the very simple to more advanced.
You do NOT have to follow the list until the end, just stop when one of the solutions fixes the issue for you (starting from #1).
1.Reboot! Yes multiple users have mentioned that a simple reboot fixes the issue.
2. Cycle Wifi off then back on. (I said we were starting out simple.. )
3.Sign out of iCloud then reboot.
4.Sign back into iCloud – For some users they are able to sign back in and not have any issues. If you sign back in and are still having issues keep going down the list.
5.Are you on 10.15.6 with this issue? Install the 10.15.7 Update.
6.Disable iCloud Drive Options > Internet Accounts > iCloud > Options Button > unselect all options – Restart
6. Disable iCloud options – Internet Accounts > iCloud Uncheck all – Photos, Mail Contacts, Calendars, Reminders, Safari, Find My Mac, Notes & Keychain – Reboot – If you get any popup messages asking if you want to keep the items on your Mac. Make sure you select “Keep on This Mac” if you need to save your keychain passwords for example. After this if the problem goes away you can attempt to re enable them.
7. Sign out of all System Preferences > Internet Accounts > added email addresses. This includes any IMAP, POP, Gmail, Yahoo. Office365 o365 or Exchange accounts. Reboot – Then see if the issue comes back. If not then attempt to re add the email accounts.
Below are medium skill level fixes
7. Delete local Mail store & preferences – Disable iCloud Mail Sync – then delete /Users/yourhomefolderhere/Library/mail & /Users/yourhomefolderhere/Library/containers/com.apple.mail – Enable iCloud Mail Sync.
8.Delete Local Items Keychain folder (BACKUP ANY PASSWORDS FIRST) – Users/yourhomefolderhere/Library/Keychains – It will be the blue folder with the UUID looking numbers. Delete this folder and immediately reboot.
9.Reset iCloud settings when you can’t sign out.
If you run this command it will do the following.
1. Kill the com.appleiCloudHelper process
2. Move your iCloud .sqlite database to a new backup folder
3. kill accountsd process
4. reboot
Open the terminal.app, then cut and paste the command below.
Below are more advanced level fixes that hope you don’t have to do.
9. Do you have time machine backups? Restore from your last good backup.
10. Reinstall (Not Erase) macOS Catalina 10.15.7 – This workaround will reinstall macOS Catalina 10.15.7 and you will be able to keep all your files and applications. All you need to do is download the Catalina Full installer from the App Store and reinstall. You can also do this by booting to recovery. Restart your mac and hold down Command R. This will boot you to recovery, just select Install macOS Catalina.
If you need any help with any of the above workarounds let me know in the comments.
Update Automatic Snapshots
Automatic Update Snapshots was introduced as a feature in macOS High Sierra. You can read about them below. This was one of the best features that Apple has ever added to macOS. Sadly this will not help you in this situation as they only work for 10.13 and 10.14 Security Updates. Apple disabled this option in 10.15 Catalina Combo Updates.
After updating macOS to 10.15.7, `accountsd` is using almost 600% CPU, for over an hour now. Using Safari for more than 30 seconds makes it hang, I have to force quit it. pic.twitter.com/yf7DXlFH44
@Apple Since today's update macOS Catalina 10.15.7. MacBook Pro 2019, i9 – 16 GB Ram. Fan is on constantly, system slow, battery % goes down with mac plugged to the electricity, accountsd 500% CPU: pic.twitter.com/a42ReehP6a
After updating MacOS 10.15.7, accountsd's CPU utilization spiked to almost 500%. I tried rebooting several times, but it didn't fix the problem. As accountsd is icloud sync process, I signed out from iCloud and re-signed in. And then, everything got back to normal. v(´-ω-｀)v
If you install Security Update 2020-005 for Mojave, you could run into major issues!
Multiple reports are coming in from users who are starting to have major problems after installing the latest Mojave 2020-005 Security Update.
UPDATE #8 – 10/01 10:00PM –Apple has just released a fix and I’ve just finished an article going over all the details. I tried to test and figure out every scenario that you might be in, so you know exactly what will happen.
UPDATE #5 – 9/28 7:30PM – I have added 3 new sections below. The first one shows you how to ignore the Mojave 2020-005 Security Update. The second will show you a very quick way to find out if your Mac is affected by this issue. In the 3rd, I will show you 4 different install scenarios. We now know the issue only happens if you install Safari 14.0 first, then install the 2020-005 update after. An example of a Mac that would unaffected by this issue would be if you installed the 2020-005 Security Update first, then the Safari 14.0 update after.
UPDATE #4 – 9/28 12:30PM – I have reproduced the install problem flow Please read section #5 below for more info. You can install the Mojave 2020-005 Security update WITHOUT Safari 14.0 and not have any issues. You can even Install Safari 14.0 after and not have any issues. It’s only when you install Safari 14.0 first then install 2020-005 after when the problems start! I will continue to test this and post updates.
UPDATE #3 – 9/28 11:30AM – After running some more tests, Safari 14.0 could be one of the problems. The next test performed was to build a fresh 10.14.6 Mac and install only the 2020-005 Security Update = No problems. I then installed Safari 14.0 = No problems. Then I reinstalled 2020-005 again = All Problems are back!!! I am going to check the order, maybe if Safari 14.0 is being installed first with softwareupdate this could be part of the problem. I am going to continue to test to find out more.
9/27
UPDATE #2 – 9/27 5:00PM – I am keeping an eye on Apple’s Software Update Server to see if they pull the update. I will update if they do.
UPDATE #1 – 9/27 3:30PM – A few users have asked if they can install the 2020-004 update over the 2020-005 update. They mentioned being able to do this in the past. Usually you can’t go backwards using Apple’s .pkg installers. I tested this out and sure enough, the installer says that a newer version of this update is installed. Apple didn’t design the installers to undo newer security updates. This is unlike the full .app installer which can replace all OS level files.
This article will include will be continually updated with the latest information on this issue.
I have some workarounds and fixes that could help you if you already installed the Mojave 2020-005 Security Update.
macOS Mojave 2020-005 Security Update Causing Major Problems Mr. Macintosh Video.
Past macOS Security Update Issues
This is not the first time that I’ve reported on update issues. Below you can read a few of the major issues that I’ve written about.
3. How can I tell if my mac is affected by this issue?
4. How can I ignore this update in software update?
5. How to Reproduce – Install Order
5. User Reports
6. This time around the issue can be reproduced
7. Fix! Rolling back with Automatic Update Snapshots. (within 24 hours of install)
8. Workarounds
9. If you are seeing this issue, please let Apple know.
10. Mojave 2020-005 Security Update Issue Links
11. Hat Tip/Credits
1. Mojave 2020-005 Security Update Problems
What are the reported problems with this update?
1. Memory issues – Reports of large increases of memory usage = no free memory and a large amount of compressed memory.
2. Slow boot & High fan speed
3. System slowness / stalling in finder
4. New local user can not be created through Users & Groups.
5. Migration assistant crashes to login window when started.
6. Large amounts of system.log entries – Class asn1SetToken is implemented in both /System/Library/PrivateFrameworks/StoreServices.framework/Versions/A/StoreServices
7. Errors when using tmutil localsnapshot /
8. Error when running softwareupdate -l (not sure if it causes any issues with the softwareupdate binary)
9. System locks up in Desktop & Screen Saver > Screen Saver when trying to select a picture type screen saver.
10. WindowServer Process using 4 times amount of memory. Should be anywhere between 40-125MB after the update it jumps to 400MB
11. cDock 4 – Dock customization app becomes unusable.
12. Menu bar sometimes does not change after switching from applications back to the finder.
1. Affected Safari & macOS Build Versions
This issue affects the following Safari & macOS Build Versions.
Safari 14.0 – September 16th, 2020
Mojave 10.14.6 Security Update 2020-005 (18G6032) – September 24th, 2020
No reports so far of this happening on macOS High Sierra 10.13.
2. Affected Mac Hardware
Past problems would only happen with certain hardware models. Not this time, if you installed the Mojave 2020-005 Security Update on a compatible Mac you might have problems.
3. How can I tell if my Mac is affected by this issue?
Very simple, just open up the terminal.app and run softwareupdate -l
If you get this error your Mac is affected.
Class AMSupportURLConnectionDelegate is implemented in both /System/Library/PrivateFrameworks/EmbeddedOSInstall.framework/Versions/A/EmbeddedOSInstall (0x1130cec58) and /System/Library/PrivateFrameworks/OSPersonalization.framework/Versions/A/OSPersonalization (0x112f31358). One of the two will be used. Which one is undefined.
4. How can I ignore this update in software update?
All you need to do is use the softwareupdate ignore option.
I discovered last night that on my Mojave test Mac that I couldn’t reproduce the issue even though I could on my 2nd test Mac. I realized that I only installed the 2020-005 Security update and NOT the Safari 14.0 update. This is when I restored back to the previous snapshot and tried again. For the next test, I let software update install both updates. Safari 14.0 was first then 2020-005, after the reboot I had the problem. Let’s go over a few of the install scenarios below.
Scenario #1 How to install both Updates and be affected by the issue.
1. 10.14.6 (18G103) Base Install
2. Use software update to install both Safari 14.0 and 2020-005 Updates
3. After the restart = You will have the problem.
Scenario #2 You installed Safari 14.0 as soon as it came out on 9/16
1. 10.14.6 (18G103) Base Install
2. Install Security Update 2020-005 + Reboot = You will have the problem
Scenario #3 How you can install both updates with NO PROBLEMS
1. 10.14.6 (18G103) Base Install
2. Install Security Update 2020-005 ONLY + Reboot = No Problem
3. Now Install Safari 14.0 = No Problem
Scenario #4 How you can install both updates with in the correct order and still have the problem
1. 10.14.6 (18G103) Base Install
2. Install Security Update 2020-005 ONLY + Reboot = No Problem
3. Now Install Safari 14.0 = No Problem
4. Install Security Update 2020-005 AGAIN + Reboot = You will have the problem (NOTE: the same problem happens if you use the 2020-004 installer in this step)
3. User Reports.
The first report came in on Thursday, just 4 hours after Apple released the Mojave 2020-005 Security Update.
Is anyone getting really low free RAM after applying this update? Activity Monitor says I have 12GB of RAM used right after I launch it after logging in.
I applied the 2020-005 Security Update today to my MacBook Pro running Mojave (10.14.6) and after it restarted, I started experiencing problems. The first and most obvious is the Dock crashes repeatedly. I have also noticed that when running applications, the menu bar does not display the app’s menus, but stays showing Finder menus. I downloaded the .dmg file with the updater on it and applied it again, thinking perhaps something went amiss the first time, but it did not resolve the issue.
After doing this job for many years, I get an sense when things are starting to become an issue. Just to be sure, I always wait for more reports and attempt to reproduce the issues myself before reporting.
Additionally, boot time is slower, logging in is slower and when doing so I’m met with a blank desktop which needs 7-8 seconds before icons finally appear. Everything feels sluggish, and applications also take more than twice as long to start up.
After reading multiple reports I felt that it was time me to take a closer look. Sure enough, more users have started to report the same issues.
4. This time around the issues can be reproduced
When issues like this have come up in the past, I might not be able to reproduce them. I have to go purely on user reports, which at times can be tough. I want to make sure the reporting is very accurate. Especially when I am recommending that users not install a security update. This time around is different, I have tested the update on multiple Macs and can reproduce most of the issues. I also found a few that have not been reported on the forums or twitter.
5. A Fix! Rolling back with Automatic Update Snapshots. (within 24 hours of install)
Do you have time machine backups?
If you do, just restore and you are good to go! Now would be a good time to start. If not keep reading.
Automatic Update Snapshots was introduced as a feature in macOS High Sierra. You can read about them below. This was one of the best features that Apple has ever added to macOS. Sadly they only work for 10.13 and 10.14 Security Updates and not 10.15 Catalina Combo Updates.
Automatic Update Snapshots could save you, if you installed the Mojave 2020-005 Security Update in the last 24 hours. That’s the problem with tmutil localsnapshots they only last 24 hours!!! So if you installed the update you might still be able to roll back to the previous Mojave Security Update 2020-004 (18G6020).
Steps to restore from an Automatic Update Snapshot.
Reboot to recovery. Hold down Command R
Once in recovery select “Restore from Time Machine Backup”
On the next screen select “Macintosh HD”. If your Mac is filevault encrypted you will be asked for your password.
On the next screen, if you have a snapshot available it will look like this.
If you have an automatic update snapshot available, this is what it will look like.
5. Select it and hit continue! Your Mac will now restore back to the snapshot taken just before the 2020-005 Security Update was installed.
But what if 24 hours has past since you installed the update? Keep reading below.
6. Workarounds
If you don’t have an Automatic Update Snapshot available, hopefully one of the following options will help you.
Upgrade to Catalina. This was recommended by Apple Support. If don’t want to upgrade to Catalina yet, scroll down to option #2.
We’d like to see how we can help. We recommend upgrading to the latest macOS Catalina by following the steps in this link: https://t.co/cCbnQHhGBJ
This workaround will reinstall macOS Mojave 10.14.6 (18G103) and you will be able to keep all your files and applications. All you need to do is download the Mojave Full installer from the App Store and reinstall. To keep your Mac protected, you can install Security Update 2020-004 and not have any issues.
You can also perform an erase and install if you have all your files backed up.
@AppleSupport@havertyj@vitahallo We operate a fleet of about 350 Macs, and are seeing issues with extreme stalling after Security-Update 2020-005 and 10.15.7. Not all of our machines, but enough that it concerns me. Standard troubleshooting has not helped… any news or help?
@Apple I installed the 2020-005 Security Update for my MacBook Air and now the computer is super slow, has no free memory left even when it just booted up, and it takes ages to start up programs. Can you give me instructions on how to uninstall the update?
@AppleSupport The newest security update for Mojave—2020-005 10.14.6—slowed my computer to a crawl and caused nearly constant freezes. I had to roll-back to a previous version. It's a late 2015 27-inch iMac, serial C02SH3TBGG7J
Multiple Hat tips go out to my website and twitter followers for reporting the issue to me so I could take a closer look. Special thanks to Hyram Hakkenbecker for double-checking my articles for any grammar issues that sneak past!
UPDATE 9/26/20 – Some users have reported major problems after installing the update!
Today, Apple released macOS Security Update 2020-005 for High Sierra and Mojave. The 2020-005 security update will most likely will be the end of the line for macOS High Sierra. After macOS Big Sur is released, Apple will no longer support High Sierra.
Below you will find Build Versions, Download Links, Update Sizes and previous Security Update Links.
What’s New in the macOS 2020-005 Security Updates – Mr. Macintosh Video.
The 2020-005 Update fixes & reverts the 2020-003 changes made to the –ignore flag. After installing the update, you can now ignore major upgrades again.
UPDATE 9/24/20 – The 2020-004 update was said to fix this but it actually did not work properly. If you had a UAMDM (User Approved Mobile Device Management) Enrolled Mac the --ignore option did NOT work. The 2020-005 update fixed this and now works properly. Big hat tip to @pcrandom for doing a ton of testing. He was able to confirm that this issue was fixed.
After installing 2020-004 on 10.14 & 10.13 you can once again block major upgrades (Catalina). I mentioned this change in my Catalina 10.15.6 Patch Notes Article.
NOTE: This change is ONLY for UAMDM (User Approved Mobile Device Management) and Supervised Macs. If your Mac is not Supervised or part of an UAMDM you will not be able to ignore major updates.
In macOS Big Sur softwareupdate --ignore is deprecated and no longer works. You will only be able to block minor and major updates for 90 days using MDM.Please file feedback NOW, if you need the ability to block minor & major updates in macOS Big Sur!Thanks for the clarification @mboylan!
How do I keep track of all the macOS Build Versions?
I document all of the macOS Build Versions like the latest Mojave 2020-005 High Sierra 2020-005 along with most Apple Applications, XProtect, Gatekeeper and MRT updates in one database. You can check out the link below.
What’s New in the macOS Catalina 10.15.7 Update (19H2)?
macOS Catalina 10.15.7 Update is now Available!
For the first time since Mac OS X Snow Leopard, Apple has progressed past a .6 point release! I’m very happy with this change, as it’s easier to understand dot releases compared to supplemental updates. This is the 21st update overall for macOS Catalina.
UPDATE! 9/29/20 – I just posted an article talking about the Catalina 10.15.7 Update accountsd process using 400%+ CPU.
UPDATE! 9/27/20 –A few reports are coming in that the 10.15.7 update is causing some problems with the accountsd process. After the installing the 10.15.7 update, accountsd runs up to 400% in Activity Monitor. The issue might happen for some users that are using iCloud for Drive, Mail or Cal. Other reports say the issue can happen if you are using internet accounts with Gmail. This issue causes system slowness until resolved. Most fixes say to log out of iCloud or Gmail then restart.
Let’s take a look at the macos Catalina 10.15.7 update changes.
What’s New in the 10.15.7 Update Mr. Macintosh video.
10.15.7 Update = accountsd process using 400%+ CPU if using iCloud Mr. Macintosh Video.
The macOS Catalina 10.15.7 Update includes the following fixes.
macOS Catalina 10.15.7 provides important security updates and bug fixes for your Mac.
Resolves an issue where macOS would not automatically connect to Wi-Fi networks
Fixes an issue that could prevent files syncing through iCloud Drive
Addresses a graphic issue that may occur on iMac (Retina 5K, 27-inch, 2020) with Radeon Pro 5700 XT
Apple’s Public Patch Notes / Release Notes Documentation
NOTE: Apple Documentation takes a little while to show up online after release. I will update when the new articles are made available.
Today Apple released macOS Big Sur Beta 8 (20A5374i) to Developers
UPDATE 9/23/20 – Beta 8 Issues
Big Sur Beta 8 does not have a full installer, hopefully we will get one when Beta 9 hits in a week or two.
No changes or additional notes to Screen Recording controls, it was noted in Beta 7 that we would get some sort of MDM controls for this for standard users.
Active Directory login is not working in Beta 8 after an upgrade. Was working fine in Beta 6 and 7.
You can take a look at my Beta 7 article, it has a list of current standing issues that might not have been fixed in Beta 8 yet.
MacOS Big Sur 11 Beta 8 (20A5374i) was released on September 22nd, 2020 only 7 days after Beta 7! MacOS Catalina had 11 beta releases including the gold master, so we are getting close to release. Beta 8 is very small and only includes one noted fix in the developer notes. I am still waiting to see if any changes are listed around screen recording or if we get a full installer. I will update as soon.
During the Big Sur beta release cycle, only the current beta patch notes are available. When a new beta is released the previous patch notes are overwritten. I compare both sets of release notes so I find the changes.
1. Note: Apple did not provide a full installer for Beta 8.
2. 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)
Previous Big Sur 11 Beta Releases
8. Big Sur 11 Beta 8 (20A5374i) – 09/22/20 – Current Release
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 Beta 8 (20A5374i) Release Notes
Overview
The macOS 11 SDK provides support to develop apps for Macs running macOS Big Sur 11. The SDK comes bundled with Xcode 12.2 beta, available from Beta Software Downloads. For information on the compatibility requirements for Xcode 12.2, see Xcode 12.2 Beta Release Notes.
General
Known Issues
Important
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)
macOS Big Sur 11 beta 8 is designated as qualifying for the 50% Apple Security Bounty bonus payment for issues that are unknown to Apple or reintroduced in this release. See Apple Security Bounty for more information.
Installer and Software Update
Known Issues
When updating from macOS Big Sur 11 beta 2 to macOS Big Sur 11 beta 3 or later, you might be offered an unexpectedly large download rather than an incremental software update. (65753086)Workaround: Under the “Another update is available” text, click the “More info…” link. This will reveal the incremental update where you can click the Install Now button.
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)
If macOS Big Sur 11 beta is installed into the same APFS container as previous versions of macOS Catalina 10.15, system software updates can no longer be installed on the previous versions of macOS. (64411484)Workaround: Update the previous version of macOS Catalina to 10.15.6.
Kernel
Resolved in macOS Big Sur 11 beta 8
An issue with the kernel no longer causes applications to quit unexpectedly. (69093270)
SwiftUI
Known Issues
ProgressView generic type signature has changed, adding the currentValueLabel generic parameter. This change doesn’t require any source changes, but will cause apps compiled using an earlier beta SDK to quit unexpectedly. (63580200)Workaround: Re-compile apps for macOS Big Sur 11 Beta 6 or later to resolve this issue.
Drag-and-drop actions can sometimes fail when dropping on dynamic view content. (68281403)
Dynamically updating OutlineGroup content can fail to update correctly or cause an application to quit unexpectedly. (58820037)
DisclosureGroup’s isExpanded binding does not work as expected in a List. (58820037)
Some standard menu items, such as Open Recents or Window menu items, are missing from the main menu. (63998004)
Third-Party Apps
Known Issues
You might experience kernel panics when using earlier versions of Parallels Desktop 16. (67358596)Workaround: Upgrade to the most-recent version of Parallels Desktop 16.
Some third-party scripts might produce unexpected results due to the change in macOS version from 10.x to 11. (62477208)Workaround: Set SYSTEM_VERSION_COMPAT=1 in the calling environment, for example: $ SYSTEM_VERSION_COMPAT=1 legacy_script.pl
isPassLibraryAvailable() doesn’t ensure uniform availability of pass library functionality between platforms and devices. (60697880)Workaround: Call a more specific API to check available functionality, such as canAddPasses().
Xcode
Known Issues
Legacy Xcode versions prior to 11.5 might unexpectedly quit when launched. (59991056)Workaround: Run the following command in Terminal: defaults write com.apple.dt.Xcode DVTDisableMainThreadChecker 1, then deselect Main Thread Checker in the Diagnostic tab of the Run and Test actions for each scheme in your project.
The Command Line Tools package for Xcode 12.2 beta isn’t currently available. (69012274)
Downgrade Big Sur T2 BridgeOS Beta to a Production Catalina version of BridgeOS.
Using Apple Configurator, you can now downgrade T2 BridgeOS Beta to a Production version of BridgeOS.
Downgrading the version of your T2 BridgeOS has never been possible. Developers and customers could only get a NEWER version of BridgeOS when updating or upgrading macOS. The ability to downgrade BridgeOS on a T2 Mac was simply not possible. This new change to Apple Configurator 2 most likely happened between version 2.12 – 2.12.1.
My quick 4 min video on how to boot your into DFU mode + restore / revive BridgeOS.
Deep Dive explanation on how to boot your Mac into DFU Mode + How to Reinstall BridgeOS with Apple Configurator 2 – Mr. Macintosh YouTube live demo.
Table of Contents
1. Why would you want to downgrade from a beta version of BridgeOS?
2. Can you Downgrade to a Lower Production version of BridgeOS?
3. Problems Running Catalina with a Big Sur Beta BridgeOS Version.
4. Closer look at BridgeOS versioning
5. The Big Sur installer is now using DeviceIDs compatibility checks.
6. BridgeOSUpdateCustomer updater
7. How to Downgrade a Beta Version of BridgeOS to a Production Version.
8. The Revive Option (for science)
9. Final Notes
1. Why would you want to downgrade from a beta version of BridgeOS?
Let’s say that you installed Big Sur Beta 6, and are now having a ton of problems. You probably want to downgrade to Catalina so you can work again. The only problem is, you are still on Big Sur Beta 6 BridgeOS version 18.16.12370. Keep in mind, your Mac SHOULD still work fine with this version. An example of this is if you have Catalina 10.15.6 installed on your Mac, your BridgeOS version is 17.16.16610. Let’s say that you need to test something on version 10.15.3. After installing Catalina 10.15.3, your BridgeOS version will NOT be downgraded to the period correct version of 17.16.13050. It will run just fine on the 10.15.6 version of 17.16.16610 BridgeOS. The same is the case if you have a Big Sur Beta version of BridgeOS and you downgrade to Catalina.
2. Can you Downgrade to a Lower Production version of BridgeOS?
If you are running macOS Beta, then you can use Apple Configurator 2 to downgrade your T2 BridgeOS to a final or production version of BridgeOS.
What about if you are running a production version of macOS? You can downgrade BridgeOS with Apple Configurator 2, but only for 1 week after a new macOS software update. Apple will unsign the previous version of BridgeOS along with previous iOS updates.
3. Problems Running Catalina with a Big Sur Beta BridgeOS Version.
Let’s say after you downgraded from Big Sur Beta to Catalina 10.15.6, you are now having problems. You might start to see weird issues or crashes? Normally you would have to wait until the next beta or the production version of Big Sur to get a stable version of BridgeOS on your Mac.
Looking at the xml file, I need to find my 2019 16″ MacBook Pro. Regular Model Identifiers or BoardIDs are not used here. You need to find the iBridge ProductID. Below is a snippet of the above .xml file. Below the version of BridgeOS = 17P6610
5. The Big Sur installer is now using DeviceIDs compatibility checks.
A change to the macOS Installer Beta was noticed by @grahampugh. He noticed that the new Big Sur installer now looks at the Mac DeviceID for T2 Systems and BoardID for older 2017 and below Macs.
6. BridgeOSUpdateCustomer updater
Now that we have the DeviceID, how do we know which version of BridgeOS is compatible for this model? The xml file gives us a clue BuildVersion 17P6610. I am used to keeping track of the BridgeOS Boot Rom version which is listed like this 17.16.16065.
The BuildVersion/BuildNumber is located inside the BridgeOSUpdateCustomer > BridgeOSUpdateCustomer.pkg > BuildManifest.plist.
BuildIdentities
ApBoardID 0x3E ApChipID 0x8012 ApSecurityDomain 0x01 Info
Apple Configurator 2 offers two options to Reinstall/Downgrade BridgeOS. Only the Restore option will help you downgrade and stay on the Catalina specific version.
Restore = ERASES YOUR HARD DRIVE + Downgrade BridgeOS
If you want to downgrade to macOS Catalina and a Catalina version of BridgeOS, the fastest way is to use the Restore option. Once the restore is complete, you will be on a the Catalina Production Version of BridgeOS and will have empty hard drive. You can now use Internet Recovery to reinstall macOS Catalina.
What happens if you chose the Revive option?
8. The Revive Option (for science)
As noted above, you have no real reason to use this option. But for science, what would happen? If you are on Big Sur Beta want to downgrade T2 BridgeOS Beta using the Revive option, you will leave your Mac in a non bootable state. This is because you are now running a BridgeOS version that is OLDER than the required Big Sur Beta BridgeOS. The good news is, your T2 Mac is smart enough to repair itself! As soon as the revive option finishes, your Mac will boot to a flashing folder alert or the Internet Recovery boot menu. If it boots to the flashing folder, just boot to Command Option R or Command R and you will get the menu below.
Internet Recovery Boot Menu
Connect to the internet and let it continue. You will be brought to a message that says,
You will get this message as soon as you are booted to the Internet Recovery environment.
A software update is required to use this startup disk.
Click Update and your mac will download the correct build of Big Sur Beta BridgeOS.
On this screen your Mac is updating Bridge OS to a Big Sur compatible BridgeOS.
Once complete, the Mac will boot back to Big Sur. The only way to avoid this would be to boot the Mac to Target Disk Mode so you could erase the drive and reinstall Catalina. That’s why if you want to have BridgeOS and Catalina on the same version the Apple Configurator RESTORE option is the way to go. Just make sure to backup everything before you start as all data will be lost.
9. Final Notes
It should be pretty rare that you should ever need to downgrade BridgeOS from a Beta version. Keep in mind this will ONLY work for beta versions. As I noted above you can’t downgrade from a 10.15.6 version of BridgeOS to say a 10.15.3 version. With that said I would love to be able to downgrade to a previous version. If it’s your job to test OS Updates, once you update one test T2 Mac it’s done. It will not perform the BridgeOS update again until the next update. I really like that Apple let’s us downgrade from a beta version of BridgeOS, the more ways for customers to fix their devices the better! A big hat tip goes out to Mr. Macintosh reader thomas089 for first testing this and commenting in my main article!
Today Apple released macOS Big Sur Beta 7 (20A5374g) to Developers
UPDATE 9/20/20 – New Big Sur Beta 7 issues.
1. Enterprise Connect 2.0.5 is not working properly. You can sign in one time, but never again. While the app is attempting to sign in, it will take attention from anything that you are working on at random intervals.
2. Security & Privacy Pane is crashing/not loading correctly. The error that you will get is “There was an error in Security & Privacy preferences.”
3. Share Audio Recordings first time sign in prompt continue button is greyed out preventing you from finishing the setup assistant. WORKAROUND – you have to hit the back button to back one step then go to the next window again.
UPDATE 9/17/20 – Confirmed Big Sur Beta 7 Fixes that are not in the developer notes.
1. SMB connection bug fixed!
2. Date & Time > Clock Menu Bar greyed out bug fixed by moving settings to Dock & Menu Bar > Menu Bar Clock
3. MDM Support for permitting standard users to allow Screen Recording is not available and is listed as a “Known Issue” in Big Sur Beta 7. Hoping we will get that MDM Support in Beta 8, as we are quickly running out of time.
MacOS Big Sur 11 Beta 7 (20A5374g) was released on September 17th, 2020. During the Big Sur beta release cycle, only the current beta patch notes are available. When a new beta is released the previous patch notes are overwritten. I compare both sets of release notes so I find the changes.
AppleSeed = x Resolved Issues x Announcements & x Known Issues – appleseed.apple.com
1. Note: for this macOS Big Sur Build, there will only be a software update available to take you from Beta 6 (20A53643e) to Beta 7 (20A53774g). If you are starting with a build earlier than Beta 6, or from macOS Catalina or an earlier version of macOS, you will need to install Beta 6 prior to updating to Beta 7. Translation = NO FULL INSTALLER FOR BETA 7!
2. 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)
3. macOS Big Sur 11 beta 7 is designated as qualifying for the 50% Apple Security Bounty bonus payment for issues that are unknown to Apple or reintroduced in this release. See Apple Security Bounty for more information.
Previous Big Sur 11 Beta Releases
7. Big Sur 11 Beta 7 (20A5374g) – 09/17/20 – Current Release
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 Beta 7 (20A5364e) Release Notes
Overview
The macOS 11 SDK provides support to develop apps for Macs running macOS Big Sur 11. The SDK comes bundled with Xcode 12.2 beta, available from Beta Software Downloads. For information on the compatibility requirements for Xcode 12.2, see doc://com.apple.documentation/documentation/xcode-release-notes/xcode-12_2-beta-release-notes.
General
Known Issues
Important
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)
macOS Big Sur 11 beta 7 is designated as qualifying for the 50% Apple Security Bounty bonus payment for issues that are unknown to Apple or reintroduced in this release. See Apple Security Bounty for more information.
Installer and Software Update
Known Issues
When updating from macOS Big Sur 11 beta 2 to macOS Big Sur 11 beta 3 or later, you might be offered an unexpectedly large download rather than an incremental software update. (65753086)Workaround: Under the “Another update is available” text, click the “More info…” link. This will reveal the incremental update where you can click the Install Now button.
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)
If macOS Big Sur 11 beta is installed into the same APFS container as previous versions of macOS Catalina 10.15, system software updates can no longer be installed on the previous versions of macOS. (64411484)Workaround: Update the previous version of macOS Catalina to 10.15.6.
Resolved in macOS Big Sur 11 beta 7
You can now update macOS Big Sur 11 beta 7, if Secure Boot is set to No Security. (63434409)
Kernel
Resolved in macOS Big Sur 11 beta 7
Third-party driver extensions now run after restarting your Mac. (67416908)
DriverKit extensions now function as expected. (67594339)
Spotlight
Resolved in macOS Big Sur 11 beta 7
You can now find an application using Spotlight without an initial launch using Finder. (64463806)
SwiftUI
Known Issues
ProgressView generic type signature has changed, adding the currentValueLabel generic parameter. This change doesn’t require any source changes, but will cause apps compiled using an earlier beta SDK to quit unexpectedly. (63580200)Workaround: Re-compile apps for macOS Big Sur 11 Beta 6 or later to resolve this issue.
Drag-and-drop actions can sometimes fail when dropping on dynamic view content. (68281403)
Dynamically updating OutlineGroup content can fail to update correctly or cause an application to quit unexpectedly. (58820037)
DisclosureGroup’s isExpanded binding does not work as expected in a List. (58820037)
Some standard menu items, such as Open Recents or Window menu items, are missing from the main menu. (63998004)
New Features in macOS Big Sur 11 beta 7
Adding a Spacer to a toolbar now creates flexible spaces. (64189289)
A ToolbarItem now automatically creates an overflow menu item. (60104785)
Use the new .fileImporter() modifier to present a system interface for importing one or more files into your app, and the new .fileMover() modifier to move one or more existing files to a new location. The following is an example of a simple UI for importing and moving files:struct FileMover : View { @Binding var selectedFiles: [URL] var includeDirectories: Bool = false @State private var isImporting: Bool = false @State private var isMovingSelection: Bool = false var body: some View { List(selectedFiles, id: \.self) { url in Text(url.absoluteString) } .toolbar { Button("Import", action: { isImporting = true }) Button("Move", action: { isMovingSelection = true }) } .fileImporter( isPresented: $isImporting, allowedContentTypes: includeDirectories ? [.item, .directory] : [.item], allowsMultipleSelection: true ) { result in do { selectedFiles = try result.get() } catch { // Handle failure. } } .fileMover(isPresented: $isMovingSelection, files: selectedFiles) { if case .success = $0 { selectedFiles = [] } else { // Handle failure. } } }}
Use the new .fileExporter() modifier to present a system interface for exporting one or more documents from your app. In this example, an app provides a simple note-taking interface for quickly jotting down some text and then exporting it to disk:struct QuickNote : View { @Binding var draft: QuickNoteDocument @State private var isExporting: Bool = false var body: some View { TextEditor(text: $draft.text) .toolbar { Button("Save", action: { isExporting = true }) } .fileExporter( isPresented: $isExporting, document: draft, contentType: .plainText, defaultFilename: "MyNote" ) { result in // Clear the draft now that it's saved. if case .success = result { draft.text = "" } else { // Handle failure. } } }} struct QuickNoteDocument : FileDocument { static var readableContentTypes: [UTType] { [.plainText] } var text: String init(text: String) { self.text = text } init(configuration: ReadConfiguration) throws { // Deserialize the document. } func fileWrapper(configuration: WriteConfiguration) throws -> FileWrapper { // Serialize the document. }}
Use the new .fileMover() modifier to present a system interface for moving one or more existing files to a new location. (66182201)
Resolved in macOS Big Sur 11 beta 7
A DisclosureGroup used outside of a List no longer causes an application to quit unexpectedly. (67780773)
sheets now correctly size to their contents. (67219542)
Multiline Text in a List now wraps, automatically growing the row height as needed. Adding a lineLimit(1) modifier to the Text will restore the the old truncating single line behavior. (50990605)
A List containing nested ForEach content now updates correctly. (62863714)
TabView now has a minimum size based on its selected tab. Adding a fixedSize() modifier to the TabView will cause it to be fixed to the ideal size of its selected tab. (59097532)
Using a TextEditor as the root view of a window no longer causes an application to quit unexpectedly. (67572104)
Drag and drop previews now appear as expected, matching the appearance of their source view. (59513411)
Third-Party Apps
Known Issues
You might experience kernel panics when using earlier versions of Parallels Desktop 16. (67358596)Workaround: Upgrade to the most-recent version of Parallels Desktop 16.
Some third-party scripts might produce unexpected results due to the change in macOS version from 10.x to 11. (62477208)Workaround: Set SYSTEM_VERSION_COMPAT=1 in the calling environment, for example: $ SYSTEM_VERSION_COMPAT=1 legacy_script.pl
isPassLibraryAvailable() doesn’t ensure uniform availability of pass library functionality between platforms and devices. (60697880)Workaround: Call a more specific API to check available functionality, such as canAddPasses().
Widgets
Resolved in macOS Big Sur 11 beta 7
When set to My Location, the Weather widget now displays the weather for that location. (66338250)
Xcode
Known Issues
Legacy Xcode versions prior to 11.5 might unexpectedly quit when launched. (59991056)Workaround: Run the following command in Terminal: defaults write com.apple.dt.Xcode DVTDisableMainThreadChecker 1, then deselect Main Thread Checker in the Diagnostic tab of the Run and Test actions for each scheme in your project.
The Command Line Tools package for Xcode 12.2 beta isn’t currently available. (69012274)
Resolved in macOS Big Sur 11 beta 7
You’re now able to launch Mac Catalyst and iOS apps using Xcode. (67356581)
Today Apple released macOS Big Sur Beta 6 (20A5364e) to Developers
UPDATE: 9/10/20 – SMB network connections are not working in Big Sur Beta 6. You will get a connection error. “There was a problem connecting to xxx”. Contact your administrator”.
UPDATE: 6:05 PM CST – As of 2:38 PM CST the full installer of Beta 6 is now available.
UPDATE 1:30PM CST – As of 1:30 PM CST the Beta 6 full installer is not in Apple’s Software Update server yet. Only the BridgeOS and 3.29GB updates are available. I guess it’s possible that Beta 6 might not get a full installer? I will update if it becomes available.
MacOS Big Sur 11 Beta 6 (20A5364e) was released on Tuesday September 1st, 2020. During the Big Sur beta release cycle, only the current beta patch notes are available. When a new beta is released the previous patch notes are overwritten. I compare both sets of release notes so I find the changes.
1. macOS Big Sur 11 beta 6 is now supported for iMac (Retina 5K, 27-inch, 2020). (67093251)
2. 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)
3. macOS Big Sur 11 beta 6 is designated as qualifying for the 50% Apple Security Bounty bonus payment for issues that are unknown to Apple or reintroduced in this release. See Apple Security Bounty for more information.
Previous Big Sur 11 Beta Releases
6. Big Sur 11 Beta 6 (20A5364e) – 09/03/20 – Current Release
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 Beta 6 (20A5364e) Release Notes
Overview
The macOS 11 SDK provides support to develop apps for Macs running macOS Big Sur 11. The SDK comes bundled with Xcode 12 beta 6, available from Beta Software Downloads. For information on the compatibility requirements for Xcode 12 beta 6, see Xcode 12 Beta 6 Release Notes.
General
Known Issues
Important
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)
Resolved in macOS Big Sur 11 beta 6
macOS Big Sur 11 beta 7 is now supported for iMac (Retina 5K, 27-inch, 2020). (67093251)
AirDrop
Resolved in macOS Big Sur 11 beta 6
AirDrop now works when System Integrity Protection is enabled. (67033173)
macOS Big Sur 11 beta 6 is designated as qualifying for the 50% Apple Security Bounty bonus payment for issues that are unknown to Apple or reintroduced in this release. See Apple Security Bounty for more information.
Final Cut Pro and iMovie
Known Issues
Resolved in macOS Big Sur 11 beta 6
The application no longer unexpectedly quits when using the Import Media window. (65543216)
You can now capture video using either the built-in camera or external devices. (63528489)
Installer and Software Update
Known Issues
You might be unable to update macOS Big Sur 11 beta 6, if Secure Boot is set to No Security. (63434409)
When updating from macOS Big Sur 11 beta 2 to macOS Big Sur 11 beta 3 or later, you might be offered an unexpectedly large download rather than an incremental software update. (65753086)Workaround: Under the “Another update is available” text, click the “More info…” link. This will reveal the incremental update where you can click the Install Now button.
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)
If macOS Big Sur 11 beta is installed into the same APFS container as previous versions of macOS Catalina 10.15, system software updates can no longer be installed on the previous versions of macOS. (64411484)Workaround: Update the previous version of macOS Catalina to 10.15.6.
Kernel
Known Issues
DriverKit extensions might not function due to a permission issue. (67594339)Workaround: After building the extension but before installing it, run the following command: sudo -S chmod -R u=rw+X,go=r+X ./ <dext path>
Third-party driver extensions don’t run after restarting your Mac. (67416908)Workaround: Reinstall the extension each time after you restart your Mac.
Resolved in macOS Big Sur 11 beta 6
The command kmutil inspect no longer returns an error on Apple silicon Mac computers. (65804541)
Messages
Resolved in macOS Big Sur 11 beta 6
Keyboard navigation to move focus between controls is now available. (63987810)
Applications that present modal UI in UIWebView delegate callbacks or that use JavaScript alert, confirm, and prompt no longer experience crashes under _WebThreadLock(). (64239727)
Spotlight
Known Issues
If you can’t find an application using Spotlight, launch the application at least once using Finder. (64463806)
SwiftUI
Known Issues
ProgressView generic type signature has changed, adding the currentValueLabel generic parameter. This change doesn’t require any source changes, but will cause apps compiled using an earlier beta SDK to quit unexpectedly. (63580200)Workaround: Re-compile apps for macOS Big Sur 11 Beta 6 or later to resolve this issue.
New Features in macOS Big Sur 11 beta 6
The ImportFilesAction and ExportFilesAction APIs have been replaced with a collection of new view modifiers.
Use the new .fileImporter() modifier to present a system interface for importing one or more files into your app, and the new .fileMover() modifier to move one or more existing files to a new location. The following is an example of a simple UI for importing and moving files:struct FileMover : View { @Binding var selectedFiles: [URL] var includeDirectories: Bool = false @State private var isImporting: Bool = false @State private var isMovingSelection: Bool = false var body: some View { List(selectedFiles, id: \.self) { url in Text(url.absoluteString) } .toolbar { Button("Import", action: { isImporting = true }) Button("Move", action: { isMovingSelection = true }) } .fileImporter( isPresented: $isImporting, allowedContentTypes: includeDirectories ? [.item, .directory] : [.item], allowsMultipleSelection: true ) { result in do { selectedFiles = try result.get() } catch { // Handle failure. } } .fileMover(isPresented: $isMovingSelection, files: selectedFiles) { if case .success = $0 { selectedFiles = [] } else { // Handle failure. } } }}
Use the new .fileExporter() modifier to present a system interface for exporting one or more documents from your app. In this example, an app provides a simple note-taking interface for quickly jotting down some text and then exporting it to disk:struct QuickNote : View { @Binding var draft: QuickNoteDocument @State private var isExporting: Bool = false var body: some View { TextEditor(text: $draft.text) .toolbar { Button("Save", action: { isExporting = true }) } .fileExporter( isPresented: $isExporting, document: draft, contentType: .plainText, defaultFilename: "MyNote" ) { result in // Clear the draft now that it's saved. if case .success = result { draft.text = "" } else { // Handle failure. } } }} struct QuickNoteDocument : FileDocument { static var readableContentTypes: [UTType] { [.plainText] } var text: String init(text: String) { self.text = text } init(configuration: ReadConfiguration) throws { // Deserialize the document. } func fileWrapper(configuration: WriteConfiguration) throws -> FileWrapper { // Serialize the document. }}
Use the new .fileMover() modifier to present a system interface for moving one or more existing files to a new location. (66182201)
Third-Party Apps
Known Issues
You might experience kernel panics when using earlier versions of Parallels Desktop 16. (67358596)Workaround: Upgrade to the most-recent version of Parallels Desktop 16.
Some third-party scripts might produce unexpected results due to the change in macOS version from 10.x to 11. (62477208)Workaround: Set SYSTEM_VERSION_COMPAT=1 in the calling environment, for example: $ SYSTEM_VERSION_COMPAT=1 legacy_script.pl
Wallet
Known Issues
isPassLibraryAvailable() doesn’t ensure uniform availability of pass library functionality between platforms and devices. (60697880)Workaround: Call a more specific API to check available functionality, such as canAddPasses().
Widgets
Known Issues
When set to My Location, the Weather widget might display weather for a different location. (66338250)
Xcode
Known Issues
Legacy Xcode versions prior to 11.5 might unexpectedly quit when launched. (59991056)Workaround: Run the following command in Terminal: defaults write com.apple.dt.Xcode DVTDisableMainThreadChecker 1, then deselect Main Thread Checker in the Diagnostic tab of the Run and Test actions for each scheme in your project.
You’re currently unable to launch Mac Catalyst and iOS apps using Xcode. (67356581)
