Version 3 is such an epic FAIL, at least on Linux.
It’s hard to believe something that worked really well in version 1.5.7 can be so borked now.
I’d suggest a serious rethink and roll-back.
After all, I bet it’s Linux and OS X users who make the most money for Insync, seeing as Google has a free, half-decent, client for Windows.
Come on guys, you can do better!
Hi, I just updated to version 3.0.23.40579 and the app never authenticates when I sign in to Google Drive via browser. Any help I can get would be much appreciated as I have sworn by this app for a long time now.
I just updated to version 3.0.23.40579 on ubuntu 19.04. Nice to see the feed starting to work. I’m having the following issue. Some files are not syncing and they appear in the Attention Required section all with the same error; no permission to remove file. I do see them there on Google Drive. These are not files I’m trying to delete. There are many files with this error but its only occurring within a few folders. The parent folders are shared from a G suite business account and I am dropping in lots of files from a personal account. I’d be happy to provide more info and logs.
I’ve seen this reported here before. It seems it didn’t help. I’ve now given up on 3.0.x altogether. Maybe 3.1 will be better. Happily using 1.5.7
I feel so very let down by Insync. They should have retained 1.x as the production version and developed 3 as a beta. Right now I’m in a position where I paid for some licences for some solid, usable software and it’s turned to c**p.
I hear you. If your OS is supported, you should be able to continue using 1.5.7 until v3 is production ready. Insync 1.5.7 builds
This release is still suffering from the same fundamental flaw under Linux: it doesn’t “see” new files added by a different Insync installation, thus they never appear on current installations.
Files deletion and modification are both propagated normally.
I still have to do multi-way rsync to keep several installations in sync. Insync can’t do that any more.
@Siamak @Konstantin_Boyandin Exact same behavior on my local install. But this affected me already before 1.5.7 - you can find multiple posts on this forum. My “workaround” is to always open the sub-folder in the GUI which then suddenly detects all folders and files and syncs them. It is so frustrating that this software is not able to deliver on it’s one core functionality that it is supposed to do well since more than a year.
I still put up with that because this manual workaround sadly is still more convenient than downloading/syncing files from the browser directly.
If there was any real alternative for Linux I would switch in a heartbeat. Sadly the alternatives do not (yet) support team shares.
Thank you for update!
In my case (Ubuntu 18.04) opening subfolder doesn’t help.
What’s also strange, many fully synced folders are displayed with yellow (‘partially synced’) icon, and there’s no obvious means to change that.
Pity the developers are too busy with more important tasks.
@Konstantin_Boyandin Do you open the subfolder in a file manager or do you use the Insync GUI? I have to open the Insync GUI and browse to the specific subfolder. Then it reloads the file structure from the online drive and downloads all missing files.
In my case (I have just checked that again):
I can’t fancy clicking “Sync” on multiple files every day, thus I use rsync.
(I wonder whether any of Insync developers actually read this, since my previous email exchange with them ended in smoke)
If this is happening for items in the root folder, check to make sure the sync option is set. Link to example Items created in cloud don't auto sync locally
Did you add this account as new so it reuploaded or as existing so you ended up with yellow check mark icons indicating ‘local-to-cloud file matching’ but not reuploaded? I think prior to 3.0.23 for me on windows, new items in folders with yellow check marks weren’t auto syncing but items in folders with green ones were.
Perhaps Insync team can clarify but I’m pretty sure yellow check marks are not indicating partial sync in the sense that some items contained aren’t synced. As I said above, pretty sure the yellow means that Insync has associated the local file with the cloud file but the file was not reuploaded, aka ‘local-to-cloud file matching’
@kyle There’s no ‘items created in cloud don’t auto sync locally’ option in my case (Linux version).
There’s ‘Sync new top-level cloud items automatically’ checkbox, and it’s checked.
Did you add this account as new so it reuploaded or as existing so you ended up with yellow check mark icons indicating file sync but not reuploaded?
Existing one. I have no fun re-syncing the entire Google Drive after every Insync upgrade.
When I place new file/create new folder in sync root, it gets propagated and is marked with green check. Consequently, files in it are synced from any device and gets propagated.
I wonder why some of my existing folders are marked with yellow check, and what exactly shall I do to make them sync again?
Correct, there is no setting called ‘items created in…’ that was a link to a screenshot showing the ‘Sync new top-level cloud…’ which actually appears to have moved in 3.0.23 to the settings icon next to ‘My Drive’
So it sounds like only items created in folders with a yellow check mark are not automatically downloaded locally by insync. This is pretty much the exact issue we had in windows which appears to have been fixed.
I asked about yellow checks in another thread:
The only way to change yellow icons to green is to unsync and then resync the item. I just tested and found that when I do so, the items are downloaded from the cloud (not uploaded to) and marked with green icon. The simplest way to change all items from yellow to green is to remove the account and re-add it as new so insync uploads/downloads files instead of doing the ‘local-to-cloud file matching’.
My observations based on user experience and various topics here, is that ‘local-to-cloud file matching’ (yellow icons) is not working correctly and leads to many problems including various sync errors (see Error AddCloudGDItemL(‘Unsupported file type:%r’, ‘?’)), most of which are solved by doing a full fresh sync.
@kyle Thanks for explanation. Well, I abhor fixing things in “traditional Windows” way (delete and reinstall), and I certainly hope I won’t need doing that after each upgrade.
Since I use file system level encryption with Google Drive (encfs and the like), there always will be plenty of “Unsupported file type” entities.
@kyle Do you have any explanation why syncing of sub-items will not work reliably? No yellow icons and not about new root folders… it happens with any content in sub-folders.
Re-syncing everything has no effect. The problem persists. I am affected since before 1.5.7 and was hoping that 3.x was any better. Sadly still the same issue.
Unfortunately, I’m not able to answer that. I’ve been using insync on multiple windows 7 and 10 machines for at least 3 years now with 6 free personal gdrives and one teams. insync 1.x worked pretty much flawlessly. I didn’t experience syncing issues until “upgrading” to 3.x. It has been rough to say the least but it seems to be functioning properly at the moment.
Can you provide more details regarding the installation? Which operating systems experience the issue, google cloud type (business, teams, personal), file types that fail to sync properly. Is your problem that items created locally get pushed to the cloud, but other machines aren’t automatically downloading the cloud files locally? Or is it that items created locally don’t get pushed to the cloud? Does this happen when renaming or changing existing files as well?
When you say “re-syncing” do you mean you manually unsynced and resynced or do you mean you removed the account and re-added as a new account rather than an exisitng account so it bypasses the 'local-to-cloud file matching’ entirely.
Might be better to start your own thread to discuss in more detail.
Thank you for taking your time writing that out.
Some more specific details:
I have reported the issues since last autumn in the forums and directly and received some first level support canned responses. Even though other users also report the issue in the 3.0.x beta threads on the forum the devs are painfully silent about this. I’ll wait a few versions longer and see if any Insync is addressing these comments at all.
Thanks for this extensive writeup. Great info here. I dug through the forum and found your previous threads going back to January. Posting links here in:
This should be a priority.