OK thanks. You don't think this will be the final release?If you're doing a clean install, at this point you might as well wait.
OK thanks. You don't think this will be the final release?If you're doing a clean install, at this point you might as well wait.
I quit buying GM 2005 forward. '99 Silverado was my last."Release canditate" is the new "GM". Apple won't use the "GM" term anymore.
Definitely not, it shows as "macOS 11.0.1 Beta" in about this Mac. It's also not rare to have several GM Seeds/Release Candidates.OK thanks. You don't think this will be the final release?
I‘m not using Catalina. Been on Big Sur. I didn’t have a problem until 11.0.1.from the watchOS 7.1 release notes:
"- Resolves an issue that prevented some users from unlocking a Mac with Apple Watch"
![]()
Apple Releases watchOS 7.1 With Mac Unlocking Fix, Headphone Audio Warnings, ECG in Korea and Russia
Apple today released watchOS 7.1, the first major update to the watchOS 7 operating system that was released back in September. watchOS 7.1 follows watchOS 7.0.2 and watchOS 7.0.3, which were bug fix updates. watchOS 7.1 can be downloaded for free through the dedicated Apple Watch app on...forums.macrumors.com
there are also plenty user reporting unlock issues with Catalina ...
I’m considering it. I never had issues with Catalina, though, and the Big Sur betas I tried worked great, too.Serious question:
Is anyone going to be a Day 1 upgrader after the Catalina mess?
Catalina was a mess for some. I had zero issues with it on my 16" MBP. I will be upgrading to Big Sur on release day. My M.O is to erase my drive and install a clean copy. Works every time.Serious question:
Is anyone going to be a Day 1 upgrader after the Catalina mess?
I have that problem with Catalina.Hopefully, this fixes the "Mac not unlocking with Apple Watch" problem that the last beta release caused. For me...at least. Never had that issue until first 11.0.1 beta.
Yes.is the public beta the same build number as the dev beta? (20B5022a)
Was not a Big Sur bug, was a WatchOS, just check last KB of WatchOS 7.1Hopefully, this fixes the "Mac not unlocking with Apple Watch" problem that the last beta release caused. For me...at least. Never had that issue until first 11.0.1 beta.
I never update day one. I have worked as a developer on some of the highest volume selling products and there are always unexpected bugs in any release. Even with hundreds of test engineers and 10,000s of beta users, things sneak through.Serious question:
Is anyone going to be a Day 1 upgrader after the Catalina mess?
Update using terminal command google it. Don’t use GUI terminal is faster and better and always works11.98 GB for the install from Catalina.
And it's stuck at 11.98 of 11.98 G with a bunch of progress bar left.....I *so* wish they'd just let us download a standalone installer instead of doing this through the software update blackhole.
It feels smoother, faster, sleeker. And video playback is fantastic.Out of curiousity, why do you love it? What's better about it?
Now reads as release candidateView attachment 1127731It now says beta 2 instead of RC.
🤦♂️ I NEVER had the issue with watchOS 7. I NEVER had the issue until macOS 11.0.1.Was not a Big Sur bug, was a WatchOS, just check last KB of WatchOS 7.1
Anyone on catalina had any luck downloading the installer from softwareupdate via terminal? Not showing up in the list (just the 10.15.7 supplemental), even though the RC does show in the gui....which just failed againTried, but softwareupdate isn't showing the RC seed (or I'm missing something)
Watch unlock worked fine for me with previous beta, and continues to work fine with just released public beta testers version 20B5022a. My watch is at latest release.I didn’t have this issue with 11.0.1 but there is a watchOS 7.1 out now that is supposed to fix Mac unlock issues
I NEVER had the issue with watchOS 7. I NEVER had the issue until macOS 11.0.1.
Latest beta of watchOS 7.1 didn’t do anything for it. For me, it started with macOS 11.0.1.
Sooooooo....wanna repeat that?
Yes. I understand people WERE having an issue with watchOS 7. However...I was not. We’re they running Big Sur? I don’t know. But, I know that I was...and I wasn’t having the issue. Even though others were reporting it.
I know what I’m talking about. It’s MY situation. I’ve been clear about this. Now, to answer your next comment. Yes. You were.
Have you checked the various posts in the AW forum on how people fixed this issue since watchOS 7? I had it happening on Mojave, and one of the earlier Big Sur public betas...🤦♂️ I NEVER had the issue with watchOS 7. I NEVER had the issue until macOS 11.0.1.
Latest beta of watchOS 7.1 didn’t do anything for it. For me, it started with macOS 11.0.1.
Sooooooo....wanna repeat that?
Yes. I understand people WERE having an issue with watchOS 7. However...I was not. We’re they running Big Sur? I don’t know. But, I know that I was...and I wasn’t having the issue. Even though others were reporting it.
I know what I’m talking about. It’s MY situation. I’ve been clear about this. Now, to answer your next comment. Yes. You were.