MacInTouch Amazon link...

macOS 10.15 Catalina

Channels
Apple, News

CTM

I have upgraded to Catalina, and I was unable to update Xcode to the latest version (11.1) via the App Store, even though I tried twice. I had to download it from Apple's developer site....
I've tried at least 5 times throughout today to upgrade Xcode, and it fails every time at about 75% of the way through, according to the circular icon. Guess I'll try to get it from the Developer site, as you did.
 


I've tried at least 5 times throughout today to upgrade Xcode, and it fails every time at about 75% of the way through, according to the circular icon. Guess I'll try to get it from the Developer site, as you did.
I posted a reply regarding this late yesterday… Anyway, in summary, I experienced the timeouts myself several times so I tried a fresh installation of Xcode on my second Mac and it worked on the first try.

Then I uninstalled Xcode from my primary Mac (using AppDelete). The update offer, naturally, was gone after that. I did a fresh “Get” from the App Store and the installation was successful.
 



I've tried at least 5 times throughout today to upgrade Xcode, and it fails every time at about 75% of the way through, according to the circular icon. Guess I'll try to get it from the Developer site, as you did.
Ditto... for a couple of days now.
 


I consider my late 2012 Mac Mini and myself to be very lucky - on the whole, Catalina is working faster and more smoothly than Mojave. But I do see one really annoying minor bug - all my .webloc files have only generic, white icons. And if I do Get Info on these files, I can't change the "Open with" app. I can change that in the System Prefs, however. My home folder permissions are right, and Safari itself works well.

Does anyone else notice this issue? If not, I may have to do a reinstall...
 


I upgraded three Macs (2013 MacBook Air, original 13-inch MacBook Pro and a 2017 27-inch iMac) to Catalina last night. The upgrade process worked flawlessly on all machines and helpfully identified a few 32-bit stragglers I'd overlooked at the beginning of the upgrade process, thus allowing me to abort the process if I had wanted.

Once up and running with Catalina, I noticed all three machines had a badge on System Prefs requiring me to update my Apple ID settings. On all machines having completed this step, the machines got stuck in an endless loop of entering the ID, waiting 30 seconds or so then asking again.

Searching the Apple forums, it appears the culprit was a corrupted keychain, and deleting the keychain folder fixed the issues.

While relatively trivial to fix, requiring a normal user to navigate to their library folder and poke around in keychains seems pretty user-hostile, and I'm really surprised this wasn't identified in beta testing. I'm also surprised it affected three quite different Macs. All have iCloud Keychain turned off.

Probably of more concern was that on my iMac after fixing the issue, System Prefs asked me for my iPhone unlock password. Given that I have iCloud Keychain turned off on all Macs, how did it even know what this was? I sync to a late 2009 iMac that can't run Catalina and have never synced to the 2017 iMac. I also don't have iCloud or wireless local backup enabled. (Yeah, I'm an old cable guy.) Anyway, I would have thought Apple would use a 2FA process and send me a text with a code to enter.

Even worse, I have a 6-digit password on my iPhone, and the dialog only provided the option to enter a 4-digit password. System Prefs had a list of all my family’s iPhones and knowing my daughter’s iPhone unlock password was only 4 digits, I selected that, entered her unlock code, and everything seemed to work OK.

My experience just underlines my perception that Catalina was rushed and many 'features' are not yet fully baked.

As always your milage may vary.

Mitch
 


Applications which started in classic Mac OS and are still relevant today for me:
  • Graphic Converter
  • iCab
... and very relevant to me as well, Karl (thanks for raising the point). iCab was used here until forced to another browser.

They are a couple of the very few apps which still adhere to the correct (cough, original) user interface guidelines, and thus are blisteringly easy to use. No need to think for a moment "now, how do I do ‘X’?". They just work. So easy to get stuff done, so productive.
 


I consider my late 2012 Mac Mini and myself to be very lucky - on the whole, Catalina is working faster and more smoothly than Mojave. But I do see one really annoying minor bug - all my .webloc files have only generic, white icons. And if I do Get Info on these files, I can't change the "Open with" app. I can change that in the System Prefs, however. My home folder permissions are right, and Safari itself works well. Does anyone else notice this issue? If not, I may have to do a reinstall...
Same here, running on a Mac Mini 2018. Right-click does work, giving you possible choices through “Open With,” or you can drag the icon into a browser window. And believe me, there are a number of other bugs, some only becoming apparent with the final release.
 


I couldn't resist playing on Catalina, and generally it's been fun, but there are some oddities I'm finding that I'm wondering if others have seen...
[snip]
2. All of my album art (for 1700 albums) was gone when I first opened Music. Gradually, over the next several hours, the art "repopulated" most of the albums, but about 150 of the albums no longer had covers... Most of them, as I look at them, were albums I had gone to find art for (usually on Amazon) and copied to them. That work will have to be redone, if I'm going to be obsessive about album art. ;-)
Same here, generally fun but a few oddities. After about 18 hours overnight, the album art is still repopulating, slowly. I'm guessing it'll take days. Don't know if the new Music app will continue that if not launched, so I'm making sure to leave it running.

I really, really, like iDevice management and access in the Finder.

Had to authorize a bunch of things that wouldn't have needed authorizing before. One time action, no big deal.

There's an unwelcome apparent change to Apple Mail. While the message list still displays columns for the normal attributes (sender, subject, date, etc.), I see no way to change the column widths or their order, and column headings are missing. Sort order is now selected via a pull-down menu rather than clicking on the now absent column headings. Not a helpful change.
 


The problem with this is that Apple will constantly hound you to change to zsh every time you start Terminal. Why should Apple care what shell you use is the main question. I've been using bash for many years and have no intention in going with zsh. So I'll have to live with the hounding message for a long time to come, I suppose.
I am curious, why the resistance to moving to zsh? I moved over to zsh in Mojave in June when Catalina was first announced and zsh was made the default going forward. From a interactive perspective I have noticed no difference in day to day activity. I actually became more productive when I found out about oh-my-zsh. With some the tweaks (like case insensitivity, context highlighting, and command auto-complete) I am actually happier in zsh.

My next step is to start moving scripts from bash to zsh. From what I am seeing, it is nearly seemless. Very few structural differences. Armin Briegel has a great series on his scriptingosx website on moving to zsh from bash.
 


As a little bonus, Apple Watch unlock computer and submit passwords work just fine with Catalina. Just two taps on the wrist, and passwords are entered. The blank space doesn't fill in, the application simply opens.
 


Econ Technologies, developers of ChronoSync, has posted a very clearly written and informative note (October 9, 2019) about the "cautions" necessary before "upgrading" to Catalina. Although it applies specifically to ChronoSync, I think it's useful reading for others, too. Here's the link:

 


Same here, running on a Mac Mini 2018. Right-click does work, giving you possible choices through “Open With,” or you can drag the icon into a browser window. And believe me, there are a number of other bugs, some only becoming apparent with the final release.
Weird. On my 2017 27-inch iMac 5K, all the (five!) .webloc files on my system drive retain their icons and their default "Open with" (Safari) after upgrading to 10.15.
 


I believe that selecting, for example, all the tracks of an album (especially one ripped from CD), pressing Cmd-I (get info), clicking the artwork tab, and drag/paste an album cover image accomplishes this.
You are correct. This is exactly what I've been doing for decades.
 



I guess Catalina might update the Mac's firmware, but are there any reports of that causing problems when booting back into older macOS versions?
It seems I accidentally updated 2018 Mac Mini firmware when testing making a bootable macOS 10.15.0-19A583 Catalina USB install drive with:

The flash drive booted halfway to a prompt:
A software update is required to use this startupdisk. You can update now or select another startup disk.
Clicking "Update" brought up a progress bar:
This update will take several minutes to complete and the screen will turn off for up to minute.
After a while, and a reboot, the Catalina installer window appeared. I quit it and booted back to the internal disk's macOS 10.14.6 Mojave. But that trip to the installer seems to have updated the Mac Mini firmware, because yesterday's System Report > Hardware > Hardware Overview was changed from:

Boot ROM Version: 220.270.99.0.0 (iBridge: 16.16.6571.0.0,0)
to:
Boot ROM Version: 1037.0.78.0.0 (iBridge: 17.16.10572.0.0,0)

I made a new flash drive installer, and it boots straight into the Catalina installer.

At first, I thought that the update prompt was just an alternative to the --downloadassets option when preparing the flash drive, but it seems to have been a firmware update, right?

!f that is indeed the case, I'm happy to report that the 2018 Mac Mini still runs Mojave just fine, and I might proceed with installing Catalina on an external test drive sooner than I had planned.
 


I am curious, why the resistance to moving to zsh?
“Change is bad.” I say this only partially tongue-in-cheek. I am an interactive tcsh user vintage c. 1989. Some day I'll get around to updating my .tcshrc and .login so I can use a "modern" shell and be consistent with my typist's muscle memory. “Maybe tomorrow” (for the thousandth time).
My next step is to start moving scripts from bash to zsh.
This (and other reasons) is why I've tried to make all my scripts sh (not bash) compatible.

Nevertheless, whatever shell you love, you can use it. With current macOS that requires hoop-jumping. In the future, who knows when Apple will lock us out completely. It is illuminating and interesting to see how the battle between free (libre) and non-free software plays out.
 


I am having a lot of memory and space issues with Catalina. Mail takes forever to load any email with images. I keep getting Out of Memory errors, then the OS just quits whatever app it doesn't like (Music seems to be a prime culprit). Also disk space errors, though the volume it says is out of room has almost 9 GB free.

I'm on a trash can Mac Pro, so I don't think any of those errors is due to the machine. Then there's Adobe: can't print out of Photoshop, auto file suffixes are random or no-go, various Adobe apps randomly crashing. On the other hand, Default Folder works like a champ – what a great app!
 


I am curious, why the resistance to moving to zsh? I moved over to zsh in Mojave in June when Catalina was first announced and zsh was made the default going forward. From a interactive perspective I have noticed no difference in day to day activity. I actually became more productive when I found out about oh-my-zsh. With some the tweaks (like case insensitivity, context highlighting, and command auto-complete) I am actually happier in zsh.

My next step is to start moving scripts from bash to zsh. From what I am seeing, it is nearly seemless. Very few structural differences. Armin Briegel has a great series on his scriptingosx website on moving to zsh from bash.
The resistance comes about due to my having about 1 zillion scripts which were done in bash and not having the time, nor inclination, to move all 1 zillion to zsh.
 


Ric Ford

MacInTouch
I am having a lot of memory and space issues with Catalina. Mail takes forever to load any email with images. I keep getting Out of Memory errors, then the OS just quits whatever app it doesn't like (Music seems to be a prime culprit). Also disk space errors, though the volume it says is out of room has almost 9 GB free
9 GB of free space is not really, um, “viable.” You should free up about ten times that amount, and I expect everything will work much better (if the free space underallocation hasn’t already worn out your SSD, which you might want to check with a SMART utility, such as Drive DX).
 


The resistance comes about due to my having about 1 zillion scripts which were done in bash and not having the time, nor inclination, to move all 1 zillion to zsh.
Of course, you don't need to move any of them to zsh. I still use tcsh as a login shell (long story) and am more used to its syntax than any other shell's. As a result, my cron scripts all begin with "#!/bin/tcsh".

As for the difficulty of prepending a similar line to all your bash (?) scripts, I leave that as an exercise for those familiar with awk and sed.
 



Reminders are a mess...

My iPhone and iPad were at iOS 13.1.2, and I updated my MacBook Pro to Catalina. I specifically waited until Catalina was on my machine before hitting the Reminders upgrade button on the iPhone / iPad.

Initially, none of my devices were in sync with Reminders. After repeated logging out / in to iCloud, Reminders are in sync between my iPhone and MacBook Pro. Unfortunately, my iPad only has a partial list of Reminders, and when I access iCloud via the the web, no Reminders are on the the list.

What a mess. Seems some others have this problems and other don't. Urgggg!
 


The resistance comes about due to my having about 1 zillion scripts which were done in bash and not having the time, nor inclination, to move all 1 zillion to zsh.
Understood. But that does not preclude you from running your interactive session in zsh and just leaving your scripts running in bash. That is what I am doing. I am still building scripts in bash even today.
 


The resistance comes about due to my having about 1 zillion scripts which were done in bash and not having the time, nor inclination, to move all 1 zillion to zsh.
There's no reason to convert, at least not anytime soon. As far as I know, Bash isn't going away anytime in the foreseeable future, and if it's already set as your default shell, it will stay your default shell. Your scripts will keep working. Zsh is only the default shell on newly created accounts, and it's easy enough to change the default shell to Bash when that happens.
 



I booted Catalina in VMware today to see if the problems I had were still there. Today the App Store is finally showing my purchases. A minor glitch: a purchased app showed another purchased app's icon. I wish the purchased list showed the date the app was last updated, not the date I purchased it. It would make it much easier to see what still works with current macOS versions.

I did further testing of the mouse scrolling direction. It's the reverse of what I set! Checking "Natural" gives me old style and unchecking gives me "Natural"....
 


9 GB of free space is not really, um, “viable.” You should free up about ten times that amount, and I expect everything will work much better (if the free space underallocation hasn’t already worn out your SSD, which you might want to check with a SMART utility, such as Drive DX).
To endorse and expand on that, with only 9 GB of free drive space, this is already well into hair-on-fire territory.

In addition to the working room an SSD needs for moving stuff around and erasing blocks, when a Mac goes to sleep, it saves the active RAM contents to the boot drive. Given that this is a trash can Mac Pro, I'm guessing that it has lots more RAM than 9 GB. And then there's the space required for paging virtual memory, and scratch files for Photoshop...and... and...
 


Amazon disclaimer:
As an Amazon Associate I earn from qualifying purchases.

Latest posts