![]() Update 28th November: got it up and running last week, after clearing the cache, reinstalling the app, etc. But you're allowing a third party to access you drive, which can be a dealbreaker for some of you - but it's something. I've started using this as well and can confirm that the ODrive is working. Update 19th November: aj_potc mentioned a work-a-round / alternative for now, and that's using an thirdy party sync app called ODrive. They are going to look into it further, but I guess we have to wait for now. Update 12 hours after creating this post:Just contact Google Support about this issue (I do have a business account) and we've tried a few things, one of them clearing the cache and a lot of translating in between (my Mac is in Dutch language). Is there anyone that is having the same issue or someone can confirm that it is working? I'm thinking that somehow the emulator is unable to run this app correctly or something. Detach your account and try again".įor the last hour or so I've been Googling this issue, but all I can find so far is that there were some issues with Google Backup and Sync and Big Sur, but those issues were resolved in the latest beta's. When I open/config my account in the Backup and Sync app, I get the error: "something went wrong. I know this behavior from older MacBooks, where I need to open the Settings > Security & Privacy > allow Google File Stream, but this option isn't visible anywhere. When I open the Google File Stream Drive, it says I need to allow the system extension before I can use the application. Was able to install the first set of application I often use (Slack, RoyalTS, 1Password, Google Chrome, etc.) but I'm unable to install/configure Google's Backup and Sync application or Google File Stream Drive. Hopefully, one of them will click.Received my new MacBook Pro 13" 256 GB M1 today. If you are one of the users facing this issue, then try the workarounds given below. Take the claim with a pinch of salt though, as we were unable to verify if it’s true. It’s not supported yet with macOS 11 or above (Big Sur). It’s only supported up until macOS 10.16. ![]() This statement can be backed up by a user’s claim wherein they’ve said that Google Drive is not fully supported in macOS Big Sur. It could be quite possible that the app just isn’t optimized for the new architecture/environment. However, the M1 makes use of the mobile ARM architecture. Now, the previous MacBooks shipped with Intel chips which made use of the 圆4/x86 CPU architecture. Strangely enough, the issue seems limited to the latest MacBooks that ship with Apple’s new M1 chip alone. Detach your account and try again”.įollowing this, the app may crash as well. Has anyone been able to get Google Backup and Sync to work on an M1 Mac? I cannot get through the setup/installation process.Īs apparent from the above complaints, users facing this issue report that upon trying to configure their Google account in the Backup and Sync app, they get a popup saying “Something went wrong. ![]() For the last hour or so I’ve been Googling this issue, but all I can find so far is that there were some issues with Google Backup and Sync and Big Sur, but those issues were resolved in the latest beta’s. When I open/config my account in the Backup and Sync app, I get the error: “something went wrong. Previously, reports stated that the file stream wasn’t working, and now there’s the “Error: 8B227910” issue.Īs a result, there have been plenty of complaints about the same on Google Drive and MacRumors forums, as well as Reddit. Google Drive Backup & Sync users seem to be having a really hard time using the app after the Big Sur update. New updates are being added at the bottom of this story…… Original story (published on November 30, 2020) follows:
0 Comments
Leave a Reply. |