Apple Seeds macOS Catalina Golden Master to Developers

[Mitthrawnuruodo]

Hello, already installed GM version of Catalina.

All works fine without one exception.

Apple ID panel in System Preferences is asking me repeatedly for a Apple ID password.

Once I provided Apple ID password and computer password, then after a while it is asking again and again without stop.

[...]

Does any one have this issue too? Maybe someone knows how to fix it?

I had that, and it seems to have been connected to the iCloud Keychain which need a whole lot of time (and in my case at least two to three tries) to start up.

See if System Preferences > Apple ID > iCloud > Apps using iCloud > Keychain is checked or not.

Edit: I an crossing my fingers that starting the iCloud Keychain really has fixed that issue...

 

[Peadogie]

Hello, already installed GM version of Catalina.

All works fine without one exception.

Apple ID panel in System Preferences is asking me repeatedly for a Apple ID password.

Once I provided Apple ID password and computer password, then after a while it is asking again and again without stop.

View attachment 866499

Does any one have this issue too? Maybe someone knows how to fix it?

Have you tried logging out/logging in? Worth a shot.

 

[AjTee]

I had that, and it seems to have been connected to the iCloud Keychain which need a whole lot of time (and in my case at least two to three tries) to start up.

See if System Preferences > Apple ID > iCloud > Apps using iCloud > Keychain is checked or not.

Edit: I an crossing my fingers that starting the iCloud Keychain really has fixed that issue...

Keychain is not checked. I tried to enable. For a while I was enabled but now it is disabled again. How to fix it?

 

[thejadedmonkey]

Where did you read "for no reason"? I've not seen that from any credible source. Let's remember Apple is moving toward greater interoperability of apps between MacOS and iOS. It's quite reasonable to think this will demand 64-bit only apps from this standpoint alone. Who knows what other potential reasons may exist?

Because aside from any security fixes that are required, 32bit app support is nothing more than keeping around the binaries that already exist. There's nothing else that they need to do. The worst part about it is that it takes up some storage space.

 

[Mitthrawnuruodo]

Keychain is not checked. I tried to enable. For a while I was enabled but now it is disabled again. How to fix it?

I "kicked it" a couple of times, giving my iCloud password then computer password each time, then - when it still wouldn't enable - I opened Keychain Access, opened preferences and clicked Reset My Default Keychains, then went back and tried enabling it a few times more. In the end it asked for my iPad's password(!), and after that it finally enabled (after another little while) and has stayed on since that...hopefully that was it.

 

[AjTee]

Have you tried logging out/logging in? Worth a shot.

Yep, easy thing - re-login to iCloud helped. Solved.

 

[albebaubles]

Hello, already installed GM version of Catalina.

All works fine without one exception.

Apple ID panel in System Preferences is asking me repeatedly for a Apple ID password.

Once I provided Apple ID password and computer password, then after a while it is asking again and again without stop.

View attachment 866499

Does any one have this issue too? Maybe someone knows how to fix it?

Happened to me repeatedly - after about 10 entries it finally accepted.

 

[AjTee]

Have you tried logout and login again to Apple ID ?

 

[konqerror]

Because aside from any security fixes that are required, 32bit app support is nothing more than keeping around the binaries that already exist. There's nothing else that they need to do. The worst part about it is that it takes up some storage space.

It takes up RAM when both versions of libraries have to be loaded. 32 bit is inherently less secure because features like ASLR and pointer cookies aren't available or don't work as well. Finally, you have to double QA everything.

It's wrong to say you simply keep code that "already exists". Every single piece of code you ship has an ongoing maintenance cost.

 

[chucker23n1]

There was a point in time at which Microsoft was selling, as it's front-line operating systems, Windows CE, ME, NT. ... CEMENT. Make of it what you will.

It was a cute joke at the time, but there actually was no point in time where all of those were being sold. When ME came out, NT 4 had already been replaced by 2000.

 

[Mitthrawnuruodo]

Tip: Enable half star ratings in Apple’s new Music app

Open terminal and paste:

defaults write com.apple.Music allow-half-stars -bool TRUE

 

[xmacsurferx]

heh? How am I running it then? I registered yesterday for the public beta and download it. It is build 19A582a

View attachment 866409

This is the GM seed. Of course we will have to wait and see if there will be another build, but I highly doubt it.

I signed up for the public beta yesterday as well, but every time I download it (3 different times now), and I check the plist file of the installation, the build number is from Public Beta 9. Any thoughts?

 

[AjTee]

I signed up for the public beta yesterday as well, but every time I download it (3 different times now), and I check the plist file of the installation, the build number is from Public Beta 9. Any thoughts?

Frontend not refreshed?

 

[petvas]

I signed up for the public beta yesterday as well, but every time I download it (3 different times now), and I check the plist file of the installation, the build number is from Public Beta 9. Any thoughts?

No idea. I downloaded the beta two times and both times it was the latest build.

 

[xmacsurferx]

No idea. I downloaded the beta two times and both times it was the latest build.

Could you guide me to exactly where you checked the build (while file) and the version it stated? Also, after installing the Public Beta Access Utility, in Software Updates, it only says "MacOS Catalina Beta" and doesn't specify which beta number. Screenshot below is one I just took after installing the utility again.

 

[ipedro]

I also have a huge Aperture library and have not found anything that transitions the images EASILY. I did try a small Photos library and it worked OK, but clunky as I lost most of my Project structure. I have also been using LR for the past several years, but for some older images I still use Aperture.

Luckily, I have a older MacBook Air that continues to run well on High Sierra and use that for the few times I have needed to access Aperture and older images.

I now use a combo of LR and DXO PhotoLab 2 for most photo tasks. I often wonder what would have happened if Apple had not ditched Aperture and we were now all using Aperture 5 or 6!!

Ken

I still think that when you look at their roadmap so far, you can objectively say that Apple did not in fact abandon photographers. Photos has come a significant way since its launch and I think that Apple always expected it to be a long game.

Aperture, as much as I loved it, had reached an end of the road with its existing architecture so they had to rebuild it from scratch and I think that's what we're seeing in Photos. At the point we're at now, the adjustment tools that are available natively are close to what you'd get in a pro solution like Lightroom. The ability to seamlessly bring in third party tools like Pixelmator Pro, rounds out the available tools to a true professional toolset.

What still stands out and keeps professionals from using the Photos app is photos management. I wouldn't want to just throw all my work into the mix with my personal photos. I'd like a way to toggle between my personal and pro libraries, with much better ways to sort very large numbers of photos per project. I think that'll come sooner, rather than later since we're now years into the Photos app. Perhaps, the Photos library sets the foundation for another app, that is just a UI front for the same library but that has a professional user interface with more advanced file management, sorting and adjustments.

Back to the transition from Aperture, I've decided to just start moving my Aperture RAWs into Lightroom, losing the adjustments in the process but keeping the star ratings and project structure. My edited photos are all on my website as hi-res jpegs where my past clients can still retrieve them and those clients are already years in the rearview mirror that I can ever more plausibly charge them for new edits if they ask for them, having had years to download what I had given to them. Also, my editing style has changed over the years so it'll be cool to revisit some weddings or creative shoots and re-edit photos as I need them since I have the RAWs.

 

[petvas]

Could you guide me to exactly where you checked the build (while file) and the version it stated? Also, after installing the Public Beta Access Utility, in Software Updates, it only says "MacOS Catalina Beta" and doesn't specify which beta number. Screenshot below is one I just took after installing the utility again.

View attachment 866589

Download the file and when the installer starts, just go to the programs folder and right click->Get Info. This should show the version.
[automerge]1570224828[/automerge]

Hello, already installed GM version of Catalina.

All works fine without one exception.

Apple ID panel in System Preferences is asking me repeatedly for a Apple ID password.

Once I provided Apple ID password and computer password, then after a while it is asking again and again without stop.

View attachment 866499

Does any one have this issue too? Maybe someone knows how to fix it?

I had this issue on both my Macs and the solution is easy: Reboot and then instead of going to the iCloud account, first click on Internet Accounts and then iCloud. Try to enable iCloud Keychain (which is probably disabled). Input your credentials and wait a bit. Now go back to the iCloud pref pane and put your credentials to verify the account. This should work..

 

[Lounge vibes 05]

And you "know" this how, considering the final version has not been released?

Because if you are currently running Mojave, and you download the entire Catalina beta 11 installer, and install it on top of Mojave, after you agree to the terms and conditions, there’s a big pop-up that shows you all the 32 bit programs on your computer that are not compatible, and asks if you’re sure you want to install.
[automerge]1570226243[/automerge]

How do you know that? Quite often, the GM is the same as the final build, no?

Build number is longer than regular public versions, about this Mac and system preferences still call it beta, and when updating it’s called developer beta 11 and public beta 10

 

[atlatnesiti]

I just downloaded the Public Beta, how do I check the build before I install?

If you don’t know that, you shouldn’t install beta to begin with

 

[Babygotfont]

Does Skype for Business work in this build?

works for me ... 1 day of testing ... no crashes (yet) ... version 16.28.120
[automerge]1570230398[/automerge]

I have a question: will X11 still work?

xquartz version 2.7.11 works (1 day of testing though)

 

[Martyimac]

Because if you are currently running Mojave, and you download the entire Catalina beta 11 installer, and install it on top of Mojave, after you agree to the terms and conditions, there’s a big pop-up that shows you all the 32 bit programs on your computer that are not compatible, and asks if you’re sure you want to install.
[automerge]1570226243[/automerge]

Build number is longer than regular public versions, about this Mac and system preferences still call it beta, and when updating it’s called developer beta 11 and public beta 10

I did d/l the entire beta installer and at no time did pop up occur showing me all the installed 32 bit programs. The installer just went about it's business, installing Catalina on top of Mojave, and installed without any further input from me.
I'm going to chalk it up to differences in machines.

 

[everythingapplerainbow]

Good. I accidentally upgraded the reminders app on my phone, and now it doesn't sync across macOS and iOS :\

#metoo
but Reminders app failed to sync between WatchOS 6 and iOS 13 any way

 

[thejadedmonkey]

It takes up RAM when both versions of libraries have to be loaded. 32 bit is inherently less secure because features like ASLR and pointer cookies aren't available or don't work as well. Finally, you have to double QA everything.

It's wrong to say you simply keep code that "already exists". Every single piece of code you ship has an ongoing maintenance cost.

1) Any app that runs, uses RAM. You just have to have extra libraries loaded if you're running 32bit apps.
2) So make it an optional feature, and require apps to be whitelisted to run.
3) Double QA doesn't mean much in the era of automated testing. Existing, stable, shipped, and un-changing code is the least troublesome in my experience - exactly what 32bit libraries would be.
4) At the end of the day, what matters is that none of these reasons are "good enough" to pull support for a perfectly functional feature of the OS. But since "Apple knows best", they'll do it anyway.

 

[Nütztjanix]

I don't undersatnd why they are dropping support for 32bit, so if they dropped it, what do I get as the end user? I am currently using MacOS that supports 32Bit and everything is fine and snappy.If you can support older software, why not? its even more convenient.
[…]

Because when I bought an app, I wasn't expecting it to have a finite lifespan - especially one-off games that tend to be built and support dropped after a few years. Apple has been removing 32bit support for no real reason, other than to force app obsolescence.

Because aside from any security fixes that are required, 32bit app support is nothing more than keeping around the binaries that already exist. There's nothing else that they need to do. The worst part about it is that it takes up some storage space.

It's not only adding complexity and using additional RAM and disk space, but also you definitely would have people complaining why certain new features won't be available to programs relying on 32bit code. There is no way to backport new features and functions to 32bit libraries without a significant amount of additional changes and testing, ending up rewriting most of the 32bit stuff. Essentially doubling the development work. That's not gonna happen.

And besides, Apple has always been known for leaving old things behind (e.g. floppy, optical drives). 16 years after the first 64bit consumer CPU, it's time to move on and leave the past behind. No one seriously complains about not being able to run 8bit or 16bit software on today's OS …

 

[flexiboy1912]

Just a heads up people. I upgraded to the GM and it then broke my Citrix Workspace and I could no longer connect to the office "Error: "SSL Error 61: You have not chosen to trust 'Certificate Authority'..."

Loading...

support.citrix.com

I had to reinstall Mojave on one my Mac's to connect back , not nice as I was on call at the time!

Hopefully they will fix it soon