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

[OverneathVisuals]

Our team uses Premiere Pro for video editing and we save all our project files in Google Drive so that any of us can quickly access the project and make edits. This has worked seamlessly for years. But ever since the update to Google Drive that forced the use of File Provider on Mac OS, now every time one member of our team saves a Premiere Pro project file, that file appears in the auto-save folder for the rest of us. The original creator of the file sees it in the correct place, but the rest of us can only find it in the auto-save folder. It's a confusing mess. Any ideas of how to fix this? We're reaching out to our support person at Google, but I'd hoped someone on here has run into this issue.

[OverneathVisuals]

Images for reference:

First one shows the file my teammate worked on and saved today. For me it shows that it hasn't been modified since yesterday which I know to be inccorect. 

It can be found in the auto-save folder on my computer, but not on his. And no he's not opening an auto-save and renaming it.

[russellc58186992]

This is also happening to us. 

Google Drive for desktop is corrupting the save overwrite.  Instead of overwriting the save and then uploading it, it's uploading some partial hash of it, as a corrupted project.  If you "Save As"or "Save a Copy" it will upload the complete version.  But if you Command+S Save, the overwrite won't upload. The only first time a name is used will there be a complete upload. 

So in your example, "Haworth Degree Videos - ALL FINALS (2023).prproj" is the first time it was saved on google drive with that name yesterday at 4:38pm

The project was also saved yesterday at 5:16pm and a corrupt partial version was uploaded.

the project was also saved yesterday at 5:51pm and a corrupt partial verision was uploaded. 

the project was also saved today at 12:53 and a corrupt partial version was uploaded. 

Perhaps even worse, it SAYS it uploaded it securely. You get a nice checkmark confirmation that it completed.  Thats a false positive. It did not complete.

[OverneathMedia]

Ugh! Yeah, this is detrimental to our workflow. It's good to know we could "save as" every time, but for now, we are now saving files locally on our network storage instead of on Google Drive. I hope this is resolved soon.

[Bruce Bullis]

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?

[OverneathMedia]

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?

[OverneathMedia]

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

[Bruce Bullis]

> 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?

[OverneathMedia]

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. 

[Bruce Bullis]

> 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...

[OverneathMedia]

 

[OverneathMedia]

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.

[russellc58186992]

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.