At the very least you should back up your device first so that you can roll back if necessary - officially there is no other way other than performing a factory reset.
I had my main laptop crash exactly once - and I think it was due to a buggy kext trying to force its way into the kernel. It hasn't happened again.
There have been a few aesthetic bugs related to the automatic handling of dark/light mode, which can now be enabled without external help (I used to rely on f.lux to get dark mode in the evening). These are pretty benign and don't cause me trouble.
Other than that, macOS Catalina has been smooth sailing, even at compiling software, installing stuff via homebrew, developer tooling - I do mostly Python and Golang stuff but Ruby has been rock solid too.
iOS 13 also brought me a few visual bugs which don't (gah) bug me too much, and I had a few app crashes but nothing horrible either. My bank apps don't work on it yet so I'm currently relying on desktop browsing or other banks, depending on the situation. Not a huge deal either.
Battery life doesn't seem to be suffering on either platform, differently from my experience with previous betas.
That way, you can switch between your ‘normal’ OS and the beta, and reverting is a matter of deleting the volume you created for the beta (https://support.apple.com/en-ca/HT208891)
Of course, that is riskier than installing on a separate disk or even Mac, as the beta PS could easily damage both volumes.
Bugs I've seen:
- Random graphical artifacts/issues related to dark mode.
- BT sometimes disconnects/reconnects - is this really any different than BT normally? ;) - just hit play again usually works.
- Camera app occasionally crashes.
- Tapping the lock screen with the pencil brings up the last note, but sometimes I still have to FaceId to make the note editable.
Battery life has seemed slightly worse to fine.
It's good to remember this is beta software, but the adjectives used to describe the poor quality of this beta have been a little over the top IME.
I have been using it to test the new features in Xcode 11/ iOS 13, and it has spared me many headaches.
Which is fine, betas are not supposed to be bug free. But people who had great experiences with the 11 & 12 public betas might be lulled into a false sense of safety.
But that’s just my experience.
No catastrophic bugs or crashes so far. Everything seems performant, but I feel that battery charge lasts less than it should/did.
One serious bug is that App Store apps cannot seem to update, or even be installed on the Mac.
However, based on my experience with the iOS 11 and 12 betas, I'm confident that most of the issues will be fixed pretty quickly.
11. As expected and previously announced, support for 32-bit processes/i386 architectures has been removed.
Printer drivers are also deprecated in Catalina. A future version of macOS will remove support for them completely.
24. “lpadmin: Printer drivers are deprecated and will stop working in a future version of CUPS”. man lpadmin on a macOS Catalina system for more details. It seems that Apple wants admins to move from lpd/smb/socket (JetDirect) to AirPrint.
Hopefully by "printer drivers" they mean "printer manufacturer supplied drivers" and not "all drivers that aren't AirPrint". My printer uses a driver that's built in to MacOS, hopefully it can continue to do so.
They invariably and up doing terrible things (why does a printer driver ever need a kext).
What they are saying is “your printer better support generic content formats” - AirPrint already forces that concept
This isn’t just theoretical. The first widespread security vulnerability that I remember in Windows where you could easily run command line programs on a remote server just by changing the character encoding was caused by Microsoft not testing one of the seven or eight methods they had for defining a string.
You can read Raymond Chen’s Microsoft blog to get a first hand account of all the hacks they had to put in Windows to support backwards compatibility.
On another note, if rumors are to be believe that they are moving Macs over to ARM, they have to get rid of 32 bit code. Apple’s ARM chips got rid of the 32 bit ISA.
Is this referring to QuickTime 7, the separate download?
> These incompatible media files were typically created using formats or codecs that rely on QuickTime 7—an older version of QuickTime that is included in macOS Mojave for compatibility purposes. However, because versions of macOS after macOS Mojave will no longer include the QuickTime 7 framework, you’ll first need to detect and convert incompatible media files to continue to use those files in iMovie.
What bugs me with Catalina is that my iMac Pro keeps rebooting when left unattended for an unpredictable but short time. I fixed that for now by using "Owly" which keeps it awake ...
caffeinate(8) — prevent the system from sleeping on behalf of a utility
more info - https://blog.sindresorhus.com/lungo-b364a6c2745f
Like Owly though, safe install from AppStore as well and then just sits in the menubar and lets me forget about it.
Since macOS is always released in September/October, people are speculating there will be an event for updated Macs at that time. The iMac Pro is also long out of date, and maybe they have more to talk about with the Mac Pro.
Both will permanently be in the past, but one major version away from compatibility. It’s pretty frustrating.