Insync failing to pull updated files from Google Drive

Bugs and issues Linux
1

I have markdown files that I updated on my phone and synced to Drive from there, but Insync on my desktop does not seem to recognize that there are changes. I closed and reopened Insync, paused and resumed it, and even uninstalled and reinstalled it. The updated files appear in Drive when I click “View on Drive Web,” so Google Drive has the latest version. Somehow Insync isn’t seeing the changes even though I watch it scan those folders when it starts up.

I’m on Linux Mint 22.1 Xia using Insync version 3.9.4.60020.

Has anyone else had this issue before?

2

A quick update: I unsynced the entire folder and started a new 2-way sync to the same location, and now old files have the right updates, but it did not download any new files made since the issue started occurring, even though they have the same modification date as files that did get downloaded. If everything came fresh from the cloud, why would Insync be ignoring certain files and not others?

Edit: It’s not syncing the moving of files either when I changed their location in Google Drive.

3

Hi @Dexter_Bravo! This is such an unusual case because you are absolutely right: if your files are 2-way synced (and given that you just unsynced-resynced them to the same location) all files selected should be pulled from the cloud to your Base Folder aka sync location.

Could you please send these to support@insynchq.com:

  • A screenshot of what you see on the Insync app showing the files that were downloaded, and the files that were not
  • A screenshot of your Base Folder showing what has been downloaded
  • A screenshot of errors, if you see any
  • Your log files. We’ll need the logs.db and out.txt files, which you can collect by following this guide.

Please don’t forget to include the link to this Forums post in your email. Helps me know it’s you. :slight_smile:

4

I am also having this problem – or a similar one. I have one folder that is actually synced, but Insynch is showing a red X next to the folder; and I have 2 other folders with files in them that need to be created/synced from Drive that also have the red X next to them and have not been.

5

Hi @Michael_Matson! My apologies for the trouble here. Could you check if you can see any error messages?

If not, could you try restarting Insync, and let me know if the red X’s persist?

6

To answer in order:

No, there are no error messages. I had checked that before reporting the bug and it’s one of the weird things about this – as far as I’m concerned.

Second, I killed the process and restarted In sync as you requested, The red X’s are still there in all the places they were before: The folder that is actually synced (but Insync thinks its not) and the folders with files created on Drive that it refuses to down sync.

Sorry about that. When you suggested restarting, I got hopeful for a moment.

7

No apologies needed, @Michael_Matson! Thank you for trying the steps and for updating me here.

Please send your log files to support@insynchq.com after quitting Insync, and include the following:

  • logs.db
  • out.txt
  • name of the folder/s with the red X’s
  • the link to this Forums post

Here’s how to locate those files: Locating the log files | Insync Help Center

Thank you!

8

Okay. Thanks Mia. I’m on the road for the next two days, but when I get back to my computer on Thursday I’ll send in the logs.

1 Like
9

Sure thing, @Michael_Matson! Safe travels to you.

10

Thank you! :slightly_smiling_face: I just sent the email in with the logs, a list of the problem files, and a bit more context.

1 Like
11

Email received. Thank you very much @Michael_Matson!