“smb big sur”

I have the latest Big Sur 11.0 Beta (20A5395g) installed on an external NVMe with nothing but Big Sur on it. When booting into it, the Big Sur volume/container that is exposed in Finder is read-only, and there is no Big Sur Data container, as is shown in Disk Utility. I think I remember that in prior betas the exposed Big Sur volume was the read-write Data container, and not the read-only System container. As it appears right now, I can't write anything to Big Sur. I should add that the internal NVMe of my MBP 2018 contains Catalina, and the Catalina Data container is also shown in Disk Utility, but not in Finder. Finder only shows Catalina which is read-write (so it's really Catalina Data), so it is doing for Catalina what I would it expect to do for Big Sur (showing Big Sur Data as Big Sur in Finder). What am I misunderstanding, or what can I do to

When I tried to update/download/install Big Sur 11.2.3, from System Preferences Software Update, I get: Download failed: An error occurred while downloading the selected updates. Please check your internet connection and try again. MacBook Pro M1 2021

Big Sur 8 automatically started to update this am. update got as far as progress bar on full then 5 hours and no progress. rebooted in safe mode. what can I do?

cannot install Mac OS Big Sur

I have an app that is working correctly on macOS Catalina but in Big Sur it doesn't have access to iCloud. CKContainer containerWithIdentifier:accountStatusWithCompletionHandler: returns CKAccountStatusNoAccount and [[NSFileManager defaultManager] ubiquityIdentityToken] returns nil In System Preferences it is not even listed in the apps that use iCloud. Signing & Capabilities is properly configured and is working on macOS Catalina. On the computer with Big Sur I have verified that I have iCloud on and I have exchanged files through iCloud Drive with my iPhone. The only peculiarity of the app is that it is a Mac Catalyst app. Something similar is happening to someone? Anyone know how I could solve it? Thanks!

I have mac os Catalina 10.15.7 installed on my mac book pro but every time I try to install Big Sur after downloading the public beta access utility thing, it says no update is available....please help me out.is this because I have an unsopported mac for Big Sur?

So I made an amateur mistake and installed macOS Big Sur on a second volume in the same APFS container as my primary volume running macOS Catalina. I missed the release note warning: If macOS Big Sur 11 beta is installed into the same APFS container as previous versions of macOS, system software updates can no longer be installed on the previous versions of macOS. (64411484) So my question is this: I removed the volumes containing the macOS Big Sur beta. Will system software updates on the Catalina partition work again? If not, is there a fix other than erasing and restoring from a backup?

My app display an icon on the menu bar, and the icon source file is white. I want the icon color to follow the menu bar background color, so I set the template property of NSImageview.image to YES, like this: NSImageView *logo = [[NSImageView alloc] init]; logo.image = [[NSBundle mainBundle]; imageForResource:@LOGO_16_white]; [logo.image setTemplate:YES]; In most Big Sur and below macOS11, the icon color changes with the menu bar background color, If the menu bar has a light background, the icon color is black, If the menu bar has a dark background, the icon color is white. But on a few MacBooks, the icon color is always gray and does not change. So is this a bug of Big Sur? What should I do ? Thanks!

Is there a trick to successfully installing macOS Big Sur on an ext. drive and the drive not getting corrupted when switching back to Catalina on the internal drive? I understand the issue (64411484), about being on the same APFS container, but don't the internal and external drives each have their own container? Everything is fine until I try to switch over to Catalina, either on a T2 Mac or a non-T2 Mac. Then the entire Big Sur volume is corrupted. Are there more explicit install instructions available from Apple given the known bugs? I would really like to be able to have a stable setup that isn't corrupted each time I need to switch back to Catalina. Any tips or suggestions are appreciated.

Hello. I have a MacBook Air 2020 and I got my Big Sur update just recently. I tried to update it but my administration blocked the update. They unblocked the update but it is not showing up. I have tried to manually search for new updates but the Big Sur update does not show. Could someone help me find it or download it?

I see that Big Sur added -[NSImage imageWithSystemSymbolName:accessibilityDescription]. Unlike its iOS countertpart, there is no UIImageSymbolConfiguration that allows me to choose a different size class. Have I overlooked this? Or is it coming in a future beta?

We have the mac mini with Big Sur / ARM and wanted to update it. However: softwareupdate -l Software Update ToolFinding available software The operation couldn't be completed. (NSURLErrorDomain error -1012.) And, we also used System Preferences > Software Update and it says: Unable to check for updates and then no available updates found, please try again later. We're having stability issues and wanted to update. We're running: Darwin macarm.local 20.0.0 Darwin Kernel Version 20.0.0: Sun Jun 14 21:36:36 PDT 2020; root:Bridge_xnu-7090.111.5.2~1/RELEASE_ARM64_T8020 arm64

I have a daemon that can check for and install software updates using softwareupdate. Up to Catalina 10.15.6, the order is softwareupdate --list for each update { softwareupdate --download softwareupdate --install } if any update has Action == restart restart The above has worked so far, but starting with Big Sur beta 5, I was getting infinite loop of download, install, restart. After some trial & error, it appears that in Big Sur whenever Action is 'restart', the --install has to be paired with --restart. For example, updating from beta 6 to beta 7 would be softwareupdate --install macOS Big Sur Beta 7-20A5374g --restart This is not consistent with softwareupdate's man page, which has not been updated since 2012. Anyone else notice this change? I don't know if the pairing --install/--restart is intentional because of the new Update volume, or is a bug that will go away soon. I already files a bug regarding this, FB8700934.

Hello, I develop CLI C++11 tools that need to run on Mojave and Big Sur. When I just switched to the latter, I found that adding:-target=x86_64-apple-darwin20.3.0 to the clang++ command did the trick, but it is too tied to the present darwin version. What is the recommended way to build my tools in order for them to run both in Mojave and Big Sur? Thanks!

Since I switched to Big Sur I am unable to use the search function on Mail and, subsequent to a recent update, I have now lost the 'All Mailboxes' option and mail seems confused. It also seems that attachments are being stripped from incoming emails. HELP!