Protocol used:Google Drive
Windows 10 Pro
Before this version, when i did an update on Google Drive, i could force a refresh by right clicking in the folder and choosing refresh. This would show any updated files in Netdrive. With 3.8.385 the list will not refresh to update new files that have been updated or added.
I also went into the Advanced options of the drive and checked “Always retrieve file list from the server” and it gives the same result and doesn’t refresh the file list.
The only way i have been able to refresh the file list, is actually disconnecting the drive and reconnecting it.
Testing this with:
3.8.855 (build 855, BETA) - released 08/02/2019
Windows 10 Pro x64
Now you can force refreshing folder using context menu of Windows Explorer or macOS Finder.
I am still unable to get the folder to refresh as stated above using right click and refresh. I have tested this by adding new folders and files to the Team/Shared Drive in Google Drive through the web client and it will not show the new folder/files being added in Netdrive 3.
I am on version 3.8.866 with Google Drive and am having the same exact issue.
I have a shared drive shared between two accounts.
Account A creates a folder and uploads a file to the shared drive
Account B (owner of the shared drive) does not see that file or folder, even a week later. If I right click and use the contextual menu to trigger the new NetDrive Refresh then it shows up right away. It seems the native refresh that used to take place no longer occurs.
It would also be nice to set a “Minimum refresh interval” as well as restoring the previous refresh functionality (not sure what used to trigger it, whether it was changes in files or just timed).
I apologize for the delay, due to my line of work, i have been prepping for the hurricane.
As to what @Knackster said, if this is an API limit issue, how come the issue doesn’t come up when manually doing a refresh either by context menu or command line. If this was an API limit, would it be blocked both auto and manually?
Also just to add, i am using my own API key =)
Once things settle down here, i will work on getting you the logs you requested.