Sometimes files that you delete from SpiderOak Hive or a sync folder are unexpectedly restored. This can happen for any of several reasons. Most commonly it is caused by running old versions of SpiderOak One or Groups, and upgrading to our latest version solves it. For more information on how to upgrade, see Resolve Sync Problems By Updating Your Devices.
This can also happen if if the application is not certain if a synced file was deleted on one computer before or after it was modified on another computer. To be on the safe side, the application opts to restore the file on the computer it was deleted from rather than delete it from the other computer. This is expected behavior in such edge cases, and you may delete the unwanted file.
This can also happen to a file in Hive or a sync and when one of the involved computers has a mis-set clock. If a computer's clock is incorrect, that computer will give your file an incorrect timestamp, which One can misinterpret as having been modified after it had been deleted from another computer. Please check the clocks, calendars, time zones, and locations of each of the computers involved in the sync. Correct the clocks as needed, and enable your operating system's feature to periodically correct your clocks automatically so you don't have to fiddle with this again. Do this before continuing, or the problem will recur.
Now, how to fix the immediate problem. Change the file's timestamp. To do so, you can make a trivial edit to the file, or open a command console or terminal and give the appropriate command:
copy /b "path\to\the\file" +,,
Mac or Linux:
Give the application time to notice the new timestamp and upload the change. With the changed timestamp, you should be able to delete the file and it should not be restored again.