Insync incorrectly changed owner and version of file

Bugs and issues
#1

We are several persons using Insync 1.3.22 on Windows 10 to sync to a large common directory structure to local PCs.
Today we faced a severe issue for one sub-directory.

While 3 persons today were working locally on their PCs on files in the sub-directory then suddenly the file being worked on by one user got a new owner (checked in Google drive via web-browser) and was reset to an older version. The new version was deleted and not visible in Google drive change log (web). I.e. the new version with about 30 min work was completely lost with no ways to recover. Strange thing is that the new owner of the file did not (and has never) work on this directory (has never opened it on local PC). But the directory was syncing to his PC via Insync. This user only sync Google drive to one single PC using Insync.

Same thing happened for two different files - about 1 hour between the 2 issues.

Have anyone seen any similar issue with Insync and Google drive? Is there anything we can do to debug and investigate this issue further?

#2

Tagging our engineer @dipesh and he will get back to you.

#4

Hello @Helge_Fanebust,

If a file is found to be changed both locally and remotely, then Insync overwrites the remote file by uploading the local file as a new version/revision of it on Google Drive web, so that no data is lost. You can revert to an older version of a file on Google Drive web by navigating to the File menu -> Version history -> See version history. However, here, it seems that the file was unshared and then re-shared. Even if that was the case, Insync must not have deleted the local file if it had un-uploaded changes, it would have first attempted to upload and notified you of the failure (since it failed to upload to the now unshared file). Did the user experience any “Actions Required” item in this regard?

Did the Insync feed for that user say that the file was modified or the file was removed/unshared and then a file of the same name was shared again? You may also check what happened to the file by checking the “ACTIVITY” on the parent folder on Google Drive web. If that doesn’t help, we request you to tell us the path of the said file and send to us the Insync logs and dbs from the affected machines to support@insynchq.com so that we could look into this. The “dbs” folder, logs.db and out.txt files are located inside the C:\Users[Username]\AppData\Roaming\Insync

Thanks