Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
My 2020 MBA i3 occasionally disconnects and reconnects, even though it’s continuously plugged in. It has only happened a few times since the updated completed about an hour ago.
 
from the watchOS 7.1 release notes:
"- Resolves an issue that prevented some users from unlocking a Mac with Apple Watch"


there are also plenty user reporting unlock issues with Catalina ...
I‘m not using Catalina. Been on Big Sur. I didn’t have a problem until 11.0.1.
I realize others were, because of watchOS. I never experienced the problem. (because I was on Big Sur?)
For me, 11.0.1 caused a problem.
 
Serious question:

Is anyone going to be a Day 1 upgrader after the Catalina mess?
I’m considering it. I never had issues with Catalina, though, and the Big Sur betas I tried worked great, too.
Plus, my MBP is not the only device I could work on if things did break.

If it was my only device I’d probably hold off, though. At least for a couple of days.
 
  • Like
Reactions: BWhaler
For a brief, but full on confused, moment, I thought Big Sur was already out.
I think I must be suffering John King election fatigue, wrapped in a prickly pandemic blanket.

That said: has Apple ever had a more announcement-heavy season? I can hardly keep up.
 
  • Sad
Reactions: Babygotfont
11.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.
 
11.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.
Update using terminal command google it. Don’t use GUI terminal is faster and better and always works
 

Attachments

  • CE0B9A8C-CB8A-4AE4-AAE5-30DAA6A34447.jpeg
    CE0B9A8C-CB8A-4AE4-AAE5-30DAA6A34447.jpeg
    138.2 KB · Views: 95
  • Like
Reactions: RandomDSdevel
Was not a Big Sur bug, was a WatchOS, just check last KB of WatchOS 7.1
🤦‍♂️ 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.
 
Last edited:
  • Like
Reactions: Ladyc0524
Tried, but softwareupdate isn't showing the RC seed (or I'm missing something)
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 again
 
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
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 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.

I didn’t either and unfortunately am still having the issue. All devices have been updated.
 
  • Like
Reactions: Braderunner
🤦‍♂️ 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...
 
You’d have to be insane to install this on your work production machine

insane I tell ya

insane!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.