Environment
- OS: Linux / Android
- Software version: 2.51.0 / 1.1.20
Description
After a file is permanently deleted from Trash on the desktop client, the deletion synchronises successfully with Cloud. However, when the mobile client subsequently attempts to synchronise, the operation fails with a rename conflict for the deleted file.
Steps to Reproduce
- Ensure a file is synchronised with Cloud and available on a mobile client.
- On the desktop client, move the file to Trash.
- Permanently delete the file from Trash.
- Allow the desktop client to synchronise.
- Confirm that the desktop client synchronises successfully.
- Open the mobile client and attempt to synchronise.
- Navigate to Settings → Cloud.
- Press the Sync now button.
- Observe the message displayed at the beginning of the page.
Expected Behaviour
The mobile client should automatically synchronise the deletion of the permanently deleted file.
Actual Behaviour
The desktop client successfully synchronises the permanent deletion. However, when the mobile client attempts to synchronise, synchronisation fails.
Settings → Cloud reports:
The file referenced by the error has already been permanently deleted from Trash on the desktop client.
Additional Notes
The mobile client was not being used throughout the day. All file operations were performed on the desktop client.
Before deleting the file, the rename action was opened, but the rename was cancelled without changing the filename. The file was then moved to Trash and subsequently permanently deleted from Trash.
After completing these operations, the mobile client was opened for the first time. The desktop client had already successfully synchronised the permanent deletion, but the mobile client failed to synchronise and upon pressing the Sync now button in Settings → Cloud the rename error was reported. It is currently unclear whether the cancelled rename is related to the subsequent synchronisation failure.
Further Testing
After the initial sync failure, the Untitled.md file was manually deleted from the mobile device's local files, outside of the ZenNotes application. The Sync now action was then used in the mobile client.
The file was automatically restored to the mobile device during the sync attempt, despite the file having been manually deleted from the local filesystem.
The file was then deleted again from within the mobile client, moved to Trash, and permanently deleted from Trash. Another sync attempt was performed using Sync now.
The sync still failed, and the Untitled.md file was automatically restored again.
This suggests that manually deleting the file from the mobile device, including permanently deleting it through the mobile client, does not prevent the file from being restored during a subsequent sync attempt.
Environment
Description
After a file is permanently deleted from Trash on the desktop client, the deletion synchronises successfully with Cloud. However, when the mobile client subsequently attempts to synchronise, the operation fails with a rename conflict for the deleted file.
Steps to Reproduce
Expected Behaviour
The mobile client should automatically synchronise the deletion of the permanently deleted file.
Actual Behaviour
The desktop client successfully synchronises the permanent deletion. However, when the mobile client attempts to synchronise, synchronisation fails.
Settings → Cloud reports:
The file referenced by the error has already been permanently deleted from Trash on the desktop client.
Additional Notes
The mobile client was not being used throughout the day. All file operations were performed on the desktop client.
Before deleting the file, the rename action was opened, but the rename was cancelled without changing the filename. The file was then moved to Trash and subsequently permanently deleted from Trash.
After completing these operations, the mobile client was opened for the first time. The desktop client had already successfully synchronised the permanent deletion, but the mobile client failed to synchronise and upon pressing the Sync now button in Settings → Cloud the rename error was reported. It is currently unclear whether the cancelled rename is related to the subsequent synchronisation failure.
Further Testing
After the initial sync failure, the
Untitled.mdfile was manually deleted from the mobile device's local files, outside of the ZenNotes application. The Sync now action was then used in the mobile client.The file was automatically restored to the mobile device during the sync attempt, despite the file having been manually deleted from the local filesystem.
The file was then deleted again from within the mobile client, moved to Trash, and permanently deleted from Trash. Another sync attempt was performed using Sync now.
The sync still failed, and the
Untitled.mdfile was automatically restored again.This suggests that manually deleting the file from the mobile device, including permanently deleting it through the mobile client, does not prevent the file from being restored during a subsequent sync attempt.