Premiere Pro files in Google Drive end up in auto-save folder ever since File Provider update

Hello @OverneathVisuals,

Thanks for the message. It’s been a long time since you filed this bug. Are you still having this issue? It sounds like the team cannot directly address the problem, but let the community know the current status of your workflow with Google Drive and whether or not you are still using it. I'll move your post to the Discussions board while we await your information.

Thanks,


Kevin

In my testing, when it works correctly.... 

1) you press command-S in Premiere

2) the google drive "upload queue" shows the saved file file upload

3) a project with the long hash appears as a smaller file in google drive (you can see it pop up in the web client)

4) the project with the long hash is renamed to the project name and expanded in size to the full project.

5) the original project disapears. 

What I think has been happening is a hiccup between steps 3 and 4, where the process doesn't resolve, and you are left with both an hours old save without updates, and a temp file you can't open.

For what it's worth. This issue is not happening with After Effects files. Those are able to overwrite project files to save. Only in Premiere are we having the issue.

> As for PP autosave folder - it is located right next to the main project file in the same Google Drive folder. 

...someone must have modified its permissions, right? 

"/Users/username/Library/CloudStorage/GoogleDrive/..."  should have permissions which ONLY allow <username> to access it...

Thanks Apple....haha

As for read/write permissions - we are trying some things here with allowing disk access to see what works.

As for PP autosave folder - it is located right next to the main project file in the same Google Drive folder. 

> Is there a fix to this?

None of which we are aware*; to Apple, what you've described is completely "By Design". 

* Ok, you could set the privileges on all your /Users/username/GoogleDrive folders to "read/write for everyone!", but we would never recommend that.  🙂

> I do not believe the autosave folder is located outside of each of our user's personal directories. 

Where is the autosave folder, where PPro is able to successfully save?

Actually, upon re-reading your question. I do not believe the autosave folder is located outside of each of our user's personal directories. 

Hi Bruce!

Yes, the files DO show up in the autosave folder. So you are likely correct. 

This began happening shortly after Google Drive for Desktop forced an update on Mac machines to have the Google Drive folder location "controlled by macOS". This must have screwed up some write privileges? Is there a fix to this?

The OS decision to move File Provider sync directory into a specific User's account introduces loads of potential permissions issues. 

Those crazy GUID file names in your screenshot are the result of PPro testing whether (the user who launched) it has write privileges in that directory...and failing. 

Is the autosave folder, where those files do show up, located somewhere outside of a specific user's directory?