Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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...
🤦 ummmm...yeaah.
Look....for me....nothing has anything to do with it...except macOS...ELEVEN. POINT. ZERO. POINT. ONE.
NOT Mojave. Not Catalina. Not watchOS 7. And, no...watchOS 7.1 didn’t change anything. I think 7.1 was released before 11.0.1. Anyway...it started with 11.0.1.
But, thanks for asking.
 
  • Sad
Reactions: Babygotfont
RC here

Screenshot 2020-11-06 at 1.03.58 AM.png
 
Anyone have the RC get "stuck"? Mine downloaded 3.2gb, then prepping for 15 minutes (really 30, but who is counting) then it showed downloading with a full blue bar but did nothing for a few hours. Went back to the update screen and it started over again and asked if I wanted to update now. I hit update and... its just sitting at downloading but not actually doing anything,
 
  • Haha
Reactions: Babygotfont
Serious question:

Is anyone going to be a Day 1 upgrader after the Catalina mess?
For production machine which I rely on, usually no.

I have bunch of gear connected to my Mac (tangent panel, graphics tablet, audio interface etc) so I don't expect everything will sail smoothly on first day 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.
Still not working with 7.1 and 11.0.1

1604631284052.png
 
Still not working with 7.1 and 11.0.1

View attachment 1235572
Check this forum out:




I keep it bookmarked because I have to run thru it for each update. I’d assume macOS 11 would be the same...
 
Serious question:

Is anyone going to be a Day 1 upgrader after the Catalina mess?
It’s not advisable, but I’ve used Big Sur on my daily driver since Beta 1 and it has been solid and dependable running the stock Apple apps, Microsoft Office and iWork suites, Microsoft Outlook and Teams, as well as the other apps that I use regularly (Afinity Designer, Sketch, Agenda, Xcode and Parallels). I had a short-lived issue with Parallels that was corrected by a Parallels update. The biggest issue I had was with Xcode which I attribute to a couple of Xcode betas. I’ve upgraded to RC and things went smoothly — so I’m definitely looking forward to upgrading to the production release on Day 1. I’m running on a 16“, 32GB MBPro though so ymmv.
 
Check this forum out:




I keep it bookmarked because I have to run thru it for each update. I’d assume macOS 11 would be the same...
Did not work for me :/
 
  • Like
Reactions: Ladyc0524
Speaking of Big Sur running on older devices, has anyone been running this on a 2015 15in MBP? Any insight on this or comparing to 10.15?
I have been testing on a 2015 15in MBP. Compatibility has been excellent so far, but it has been slow whenever prompting for administrator privileges. That could be due to it being a beta.
 
  • Like
Reactions: gank41
Well, this is odd. Some see beta 2, some see Release Candidate. I see Release Candidate on my device.
 

Attachments

  • Screenshot 2020-11-06 at 10.26.31 AM.png
    Screenshot 2020-11-06 at 10.26.31 AM.png
    117.6 KB · Views: 78
  • Haha
Reactions: Babygotfont
Anyone have the RC get "stuck"? Mine downloaded 3.2gb, then prepping for 15 minutes (really 30, but who is counting) then it showed downloading with a full blue bar but did nothing for a few hours. Went back to the update screen and it started over again and asked if I wanted to update now. I hit update and... its just sitting at downloading but not actually doing anything,

It is possible that while checking the checksum something was found off, and it resorted to full download again, or maybe somewhere the download was corrupted and it had to download again. Give it some time, or what's to lose, just restart the computer and have at it again.
 
What's your build number? The beta is 20B5022a

I am downloading it, as you can see. The download detailed options did not present a build number, oddly, I had checked to see the size. On my MacBook Air 2017, this is 2.81 GB if I am remembering it correctly. Developer Portal tells me I should be getting build number 20B 5022a.
 
I am downloading it, as you can see. The download detailed options did not present a build number, oddly, I had checked to see the size. On my MacBook Air 2017, this is 2.81 GB if I am remembering it correctly. Developer Portal tells me I should be getting build number 20B 5022a.
Gotcha. A full upgrade from Catalina was 11 and change
 
  • Like
Reactions: macintoshmac
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.
I've not had any issues with unlocking with my (new) series 6 watch.

Do you use beta OS on the watch, too?

Edit: Have you tried the IT crowd trick: Turn (the option) off and on again. (Or - the bit more cumbersome - unpair and repair it). Or - if anything else fails: Try the long list supplied here: https://discussions.apple.com/thread/7735380
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.