New Insync version: 3.7.2

Releases
#1

Release notes:

  • Fix issue where re-authentication prompt is not shown in some cases
  • Fix issue wherein some errors are raised immediately instead of being retried
  • Added an app setting to sync or unsync deletions when Insync is offline

Windows 7 and later
macOS 10.13 (High Sierra and later)

Ubuntu (16.04 Xenial) , (18.04 Bionic) & (20.04 Focal)
Linux Mint (18.x) , (19.x) & (20.x)
Debian (8 Jessie) , (9 Stretch) & (10 Buster)
Fedora (27) , (28) , (29) & (30)

1 Like
Deleting local files while offline does not delete files on web once Insync is resumed (investigated, pending for fix)
#2
#3

I don’t particularly understand the ‘unsync deletions’ feature. I have questions :

  • What does this actually do?
  • Are the cloud contents then just ignored in future?
  • If so, are they ignored across all machines, or just for the machine where the deletions were made?
  • Why is this recommended for dual boot set-ups, where the same folder location is being referenced?

For dual boot, is there a recommendation about which option is more robust (OneDrive, Google Drive) overall against duplicates and unplanned file/folder deletions?

#4

Hi @philstopford,

We deployed a change in 3.6.1 where files that are locally deleted while Insync is offline are just unsynced in the cloud. Related topic here. Upon getting feedback that it wasn’t native, we reverted the behavior on 3.7.2, and instead implemented a setting where a user can change said behavior.

What does it do?

  • The setting allows you, the user, to choose how to handle local deletions while Insync is offline. By default, 3.7.2’s behavior is to sync the deletions, meaning your cloud files will also be removed once you start Insync after deleting files locally.

Are the cloud contents then just ignored in the future?

  • Only if you set the setting to unsync deletions. Otherwise, it will mirror the local deletions.

If so, are they ignored across all machines, or just for the machine where the deletions were made?

  • Just for that machine :slight_smile:

Why is this recommended for dual boot set-ups?

  • This is recommended due to instances in the past where files were incorrectly removed from the cloud (which is why we used to not recommend using the same sync folder for dual boot setups). The aim for this particular setting was to help prevent unwanted deletions for dual boot users.

Recommendation about which option is more robust:

  • Did you mean the current options in the unsync-delete setting, or Insync as an application in general :slight_smile: