Once you have a log showing the problem, please send it to us to analyze it and fix the problem. When the debug mode is correctly started, MEGAsync shows a notification that says that it is creating a log ("MEGAsync.log") in your desktop. To enable de debug mode, start MEGAsync with Ctrl+Shift pressed (Cmd+Shift on OS X), or open the settings dialog and click five times in the shield next to your email address. That way, we could see how the external notification is received, how it is managed by MEGAsync and why it doesn't apply it correctly. Please create a debug log with Computer B while you are reproducing it. If you are able to reproduce the problem. But once a synchronization is already added (it doesn't matter if MEGAsync is not running or is restarted) MEGAsync should correctly propagate the changes.
During the first scan, if MEGAsync detects missing files, it follows the most conservative approach and creates the missing files on the other side instead of deleting them. MEGAsync should recognize the external deletion (or rename) and apply it in the local filesystem, except when the synchronization is added to MEGAsync. Or maybe cryptomator on Computer B doesn't like that MEGAsync deleted his files at runtime. If those deletions are done in the virtual drive, the real files created by cryptomator could be doing something different and maybe that confuses MEGAsync. The usage of Cryptomator could be changing the scenario a bit. For us Computer B always removes the local files after the step 4.Īre you using the same account in both computers? Or are you syncing a shared folder in one of them? Hello, we have been trying to reproduce the problem but we have been unable.
0 kommentar(er)
