Anyone using Drive with macOS 14 Sonoma already?

[Tom_Sch]

Is anyone using Drive with the beta of macOS 14?

[Baldies]

Yes, and the Google Drive Desktop app is always causing high CPU and looking for file changes.  The current Dropbox Beta version works great.  Beta 2 didn't fix it, or Google hasn't addressed it.  Beta is installed on Macbook Pro with i9 and 32GB of ram.  Hopefully fixed on the next Beta release.

[cryptochrome]

What's with the expectation that "Google has to fix it"? You are running a beta version of an operating system. 

[nicoh]

These betas exist for third parties like Google to build, test and fix their software before the less technologically-inclined user installs the OS in September. So yes, there is definitely an expectation that Google fix this soon... or god help the Google Drive Support department which will be bombarded with complaints.

[jojojojojo]

Just a quick note: It's not only about the beta, like Baldies says ironically "Google Drive [...] is always causing high CPU". Which it does on every macOS version, no matter how stable/beta, and I can confirm. It's something Google still is not addressing, the same with Chrome... 

[cryptochrome]

Not always. It's not causing high CPU load on my Mac, for example. If you want Google to address potential bugs, it's best to use the "send feedback" option in the Drive client or file a bug on https://issuetracker.google.com/ (although that is a bit more demanding than the send feedback option). 

Google developers don't read this forum. 

[Tom_Sch]

Looks like Sonoma beta 3 and the latest Drive for Desktop 78.0.1.0 is working. Even though the betas are intended for developers and users and companies should wait until the final release or even for the first .1 update everything changed a bit with public betas. Especially the bug players should update their apps and tools right away. 

[claidheamdanns]

Now that Sonoma has gone live, can we get a review of how well Google Drive is working with Sonoma?

[icrew]

I've not upgraded yet, myself. (As a Mac user continuously since 1988, I'd strongly advise never upgrading until at least the ".1" revision is released.)

If you want to believe some random person on the net, I have seen the following report, which seems to also support the cautions approach:

But like I said, it's just some random person on the net (I'm not even sure what social network it was posted on), so YMMV....

[campbb]

In addition to that unattributed social media post, which I've also seen posted elsewhere, Google's official Google Drive for desktop release notes page recommends waiting for 14.1.

[16thnotes]

Updated thread is on MacAdmins Slack here. https://macadmins.slack.com/archives/C08PZM3EX/p1695989433700019

As there are 5000+ admins on that channel and 100 replies to that thread, you might like the quick summary.

TLDR: The macOS 14.0 + Google Drive for Desktop combination moving files to different Google Drive directories with no apparent reason immediately on first boot of the new OS installation was a confirmed bug by Google Support and the reference ticket and bug numbers are in the thread. Google initially blamed Apple for the new way that the OS runs fileproviderd, but subsequently released a number of updates to their own software to minimize the potential damage. 

While it appears these issues are repeatable due to the number of people confirming the issue, very few are willing to call the bug completely resolved despite Google now happy to close the ticket as resolved.

Hope that helps!