Home > Apple > Mac

Google Drive cache file location change issue on Mac [Fixed]

In this guide, we will show you various methods to fix the problem resulting from the Google Drive cache file location change on Mac. Due to this sudden migration of cached content locations, users are stuck with available offline and all their files are in a temporary nonaccessible format [.tmp]. And if you think that’s concerning, well, this is just the tip of the iceberg. 

Google Drive cache file location change

This cache directory location from /Users/username/Library/Application Support/Google/DriveFS to – /Users/username/Library/CloudStorage/ has broken numerous file links and made those files inaccessible. As a result of which, the links in documents to other files on Google Drive (especially on shared drive) are now different for different users.

Google Drive cache file location change

So whereas earlier it was /Volumes/GoogleDrive/Shared drives/filename.ext has now been changed to /Users/username/Library/CloudStorage/GoogleDrive-[email protected]/Shared drives/filename.ext. Even the ‘Streaming location for Google Drive’ option has been grayed out and you could no longer change its location.

Google Drive cache file location change

If you drag a file from Google Drive to the Desktop (or any other folder), then it tends to move the file rather than copy it as it would previously. In this regard, users got in touch with Google Support, and according to him/her, here’s what the support had to say: “It’s an update from Apple that have changed the location of Drive folders not Google”.

Google Drive cache file location change

Well, this blame game will keep on going till eternity, but in between all this, many small and large organizations are continuously losing their valuable data and time. So is there an end to this fiasco? Well, there does exist a couple of nifty workarounds that might help you fix the problem resulting from the Google Drive cache file location change issue on Mac. So without any further ado, let’s check them out.

Fix Google Drive cache file location change issue on Mac

Google Drive cache file location change

It is recommended that you try out each of the below-mentioned workarounds and then see which one spells out success. So with that in mind, let’s get started.

FIX 1: Disconnect your account from Drive

  1. To begin with, quit Google Drive for Desktop from Activity Monitor.
  2. Then open Terminal from Launchpad > Others and execute the below command

    touch ~/Library/Application\ Support/Google/DriveFS/fp_left_beta
  3. Now restart Google Drive and log in via your account.
  4. You will now have a second folder that is not controlled by FileProvider and can be safely used.

FIX 2: Set Sharing Permission to “Read and write”

In the finder window, under Locations, you should set Sharing Permission to “read and write” instead of the default “read-only” setting. To do so, right-click the Google Drive folder in “Locations”, select “Get Info” and under “Sharing and Permissions” change the setting from “read-only” to “read-write.” Set it under both the “Everyone” as well as the “User” settings.

That’s it. These were the two different methods that might help you fix the issue resulting from the Google Drive cache file location change on Mac. As far as the official stance on this matter is concerned, the developers are yet to acknowledge this issue, let alone give out any ETA for the rollout of a fix. As and when any of these two things happen, we will update this guide accordingly. In the meantime, the aforementioned workarounds are your best bet.


Share:
  • Pratyush

    Hi Sadique!

    Thanks for the explaination. I had faced similar issues around feb 2023, asd I upgraded to mac OS Ventura. But I used this technique of creating a fp_left_beta file and it worked like a charm!!! Again in march, this issue reappeared, where Googledrive is mounting to /Library instead of /Volumes. I tried the similar technique but it doesn’t work now. Should I delete the fp_left_beta and recreate it once again? Any help would be appreciated.

    Thanks
    Pratyush

  • This used to work but now it has stopped working