When Insync resyncs it deletes files and re-adds them again.
this puts tons of file into my local recycle bin and then re downloads the same file again and again. These are old files I have not touched it ages.
I have just clean everything up and Insync failed, so was forced to restart, and it is doing it again, and it failed again.
it is destroying my confidence, I do not know what is safe and what is not, the only thing I can rely on it Onedrive recycle bin, but what might have been deleted in the last 30 days???
I will stick with this and help find the issue, but I can no longer trust Insync to stop destroying the software, to many issues for far too long.
So much wasted time, but I will give support a chance to fix this but they better not run the support process with me, I have had enough of it over the years.
Setup:
OneDrive Family License
MacOS: 15.3.1
Insync: latest 3.8.7.50505
Seconded. Has been happening to me too. Have spent untold hours trying to ensure that important files have not been lost. I totally agree that it destroys your confidence in the product.
This issue is present in a similar form on Arch Linux as well.
Kernel 6.14.6 running Insync 3.9.6.60027.
2-way sync config, writing a new file to the local directory that is a sync target causes the deletion of the local instance. It also causes the directory to temporarily “disappear” in the Insync client as well. Refreshing the view will allow me to see the directory again in the Insync client, and it triggers a sync operation that recreates the top level locally. It does not populate or sync any subdirectories or child objects until I begin traversing the remote file structure through the Insync client.
This is leaving a ton of garbage on my local disk and make using the software quite cumbersome, as I’m having to run through this process every single time I write a file.
My initial observation is that this might be related to an issue discussed here, assuming that none of the cloud files have been affected. To put things back in order, it is highly recommended to remove your account and add it again. Please let me know if that has been done on your end.
This was a OneDrive sync issue. Will need to continue to validate, but the issue may be resolved for now. Deleting the ~/.config/Insync and ~/Insync directories (actually renaming them to trigger creation of new directories) seems to have at least temporarily alleviated some of the symptoms.
Guys,
This is a really concerning situation.
Deleting all my files from my local is only one bad piece of code away from deleting everything from Onedrive also.
This is a potentially catastrophic failure, and bad code like this should not creep into production.
Insync it is not satisfactory for us to just delete cache or re-install.
When will this bug return and next time wipe our entire local and cloud data stores.
I do not think I can honestly use this software anymore. I will try, because you are the opposite of Microsoft; but to be fair I think your dev team needs a good shake up, and I would like to know what you are going to do internally that will stop these bugs from reaching Prod, and keep us as customers.
Rest assured that this remains on high priority investigation, and we are working on releasing a fix as soon as possible. We understand that a long-standing issue like this erodes your trust in Insync-- and we hear you. Thank you for continuing to use your voice to send honest feedback, reports, and urging us to address this matter accordingly.
Thank you for letting me know, @bravo.mike. I will update the main thread I linked above (here, for your convenience) as well as all related threads on Forums as soon as the fix is ready.
