Be careful when you hit the Unmount button

Overview

[ Icedrive desktop app ] [ Version 3.22 ]
[ Windows 10 ]

Issue

At start up, Icedrive is unmounted and synchronization works fine. If you then hit the Mount button, it continues to work fine.

However, if for some reason you then would like to unmount again, Icedrive starts to behave erraticly. Below are my findings, but the bottom line is: never press the Unmount button, because from that moment on synchronization is faulty. If you want to unmount, restart the desktop app instead.

This bug is a major one, because it easily results in an incomplete backup without the user noticing it.

Detailed description
See also the screenshots below.

  1. Just after starting the app: everything works fine.
  2. After mounting for the first time: everything still works fine.
  3. After unmounting: file deletion is correctly mirrored in the cloud, adding files is not. (*)
  4. After mounting again, the problem persists: file deletion is correctly mirrored in the cloud, adding files is not.
  5. After unlocking crypto: everything works fine again (back to situation 2).

Note that:

  • screenshot 3 is exactly the same as screenshot 1, yet Icedrive behaves differently.
  • after mounting for the first time it is impossible to get back to situation 1, where Icedrive is both unmounted and correctly syncing.

(*) Adding files results in this log entry: “[20.10.2024 11:44:17.881] [18088] crypto locked for task -1310479893; will not upload test5.txt”.

2 Likes

Sync is actually triggered when you next start the app however if you’re making changes to the local folder the app does need to be running when making the changes in order to recognise them for it to then sync the next time you open the app.

hello Chris, maybe my misreading but does the sync not happens real time the moment the app is active and any changes were to be made in a synced local folder? as if this is not to be case and the app needs to be restarted for any changes to take effect then the call from many to have a sync now button becomes something to consider

Hi @Chris , first of all, I think Icedrive should give a warning whenever a restart is necessary to resume normal operation.

Having said that, I did some additional testing to see what happens after restarting the app. Unfortunately, the problem persists. To be more precise:

  1. Any file you add to the local folder after having pressed the Unmount button, will no longer be uploaded to the cloud (even though the app is still running)—as described above. The log reports:

[21.10.2024 14:45:24.215] [20648] crypto locked for task -2132799905; will not upload test1.txt

  1. If you then close the app and start it again, synchronization works fine for new changes, but the file in question is still not being uploaded. The log reports:

[21.10.2024 14:46:45.830] [20292] checking pending uploads…
[21.10.2024 14:46:45.835] [20292] adding pending upload to a queue: fileId= -2132799905 destId 59705670 syncId 10082
[21.10.2024 14:46:45.835] [20292] crypto locked for task -2132799905; will not upload test1.txt

I hope I have provided enough information for the developers so they can look into this.

Wait what? The app doesn’t actually compare the local and cloud folder for changes, but only recognizes changes to the local folder that happen when the app is running?

I’m flabbergasted if that’s actually the case.

1 Like

Yes, that is the case. See for example:
Sync only picks up if app is running when files changed

1 Like

@FrankS I share your flabbergasted-ness. @Guido Thank you for confirming that the situation is, indeed, this insane. I saw your post and a few others on the subject, and I noticed missing items from my syncs, but I guess I just dismissed posts like this as “bug reports” and didn’t have time to get into the weeds on the details. This isn’t a bug, because it’s not unintended / unexpected behavior. It’s a completely absent crucial feature. And it’s a regression from version 2 of the app. And even more infuriatingly, it’s a downgrade from a feature that previously existed, that most (I’m going to assume almost all) users expect, that IceDrive did NOTHING to inform users of. Why, oh why, do we keep falling for this? @Guido The problem here is that there seems to be a mismatch of intent. You and others are trying to troubleshoot this as though it’s a problem that the team may not have known about, or just need more details from users in order to sort it out. Unfortunately, it appears that this is just the intended behavior. They’re not confused about it and don’t need help with it. It’s not that they didn’t know, it’s that they didn’t bother to make it work as any reasonable user would expect such a feature would work, and didn’t bother to inform any of us who might mistakenly rely on this software.

Let me restate it plainly for anyone else who is late to the party and might have mistakenly trusted the ID team to include a proper “sync” feature in an app whose main function is… you know, syncing, or who may have mistakenly trusted them to inform the end user if it lacked obvious basic functionality:

PSA: THE SYNC FEATURE ONLY SYNCS WHEN OPEN. IF THE APP IS CLOSED AND CHANGES ARE MADE, NONE OF THOSE CHANGES WILL BE REFLECTED IN YOUR SYNC PAIRS. EVER. EVEN UPON RESTARTING THE APP. IT WILL NEVER REFLECT ANY CHANGES MADE WHEN IT IS NOT OPEN. You’re welcome.

@Chris @Tom @JimmyB and any others I have missed on the IceDrive team: This is absolutely pathetic. Please, for the love of god, do better. After all the hype, waiting, and testing of version 3, you come out with… THIS? Yet another regression, removal of a previously available feature, and ABSOLUTELY NO EFFORT TO NOTIFY THE USERS AFFECTED other than those of us who dig through forum posts like this? And the most you can muster is an unenthusiastic “oh, yeah, that’s just how it works” after users have made good-faith efforts to help squash a “bug” that is really just a complete falling down of app design? This obvious feature was available in version 2 of the app. I would, upon discovering this lack in version 3, revert to version 2, but you have made it so that version 2 no longer works with your system so we are all stuck with whatever you decide to ship out. Well played.

I’ll go ahead and do what it seems you’re pushing users towards: I will put less strain on your network by no longer using the “sync” feature, only using ID as a “cloud backup” and looking for greener pastures to safely store data. I get that we should never rely on any one backup solution, and a service like this should never be used for “mission critical” stuff but geeeez, at this point I’m having a hard time coming up with a use case for even the least important files being stored at Icedrive.

For the love of god, can you guys please either actually make a working sync once and for all, or just declare it dead and announce that IceDrive is ONLY for use as a cloud backup? People do actually depend on this stuff, you know.

5 Likes

couldn’t agree more as I Also said this is not how any cloud sync system works or should work never seen this. I really wonder other than some cosmetic layout changes and some added sync potential for a Mac we seem to be going backward versus 2. … IMO

2 Likes

@tambo I definitely share your sentiment. I have been following this forum for over a month now, and it strikes me that Icedrive doesn’t show any urgency to address issues that threaten the integrity of their users’ backup. I find this very troublesome, and a loud wake-up call is needed indeed.

1 Like

Yeah, this is absolutely bonkers.

I need to sync my work files across several devices, so the risk of not syncing and losing something is a no go.

I was already looking into another cloud solution before, but decided to give the updated app a chance. Well, there we have it, I guess.

1 Like

@tambo - these are my thoughts exactly. I thought I was doing a service by pointing this out, not preaching to the converted. Like you, I also thought V3 was a regression. What happened to the periodic scanning we had before? That would solve this issue straight away.

If I turn off Dropbox for a while and reboot the next day, the app will pick up everything it missed.

Why can’t Icedrive show the same behaviour? Either reinstate the periodic scanning or copy what Dropbox does please!

2 Likes

@FrankS @tambo not only dropbox…OneDrive, google one, pcloud, mega you can name them all … all sync/ backup soft do that. its amazing how icedrive dropped the ball on this one

2 Likes