Warpinator may delete files on receiver after interrupted transfer

Distribution

Linux Mint 22.3

Package version

2.0.2+zena

Frequency

Always

Bug description

Warpinator can cause accidental data loss on the receiving device after an interrupted transfer.

If a file transfer is interrupted and later resumed, Warpinator may delete files on the receiving device that no longer exist on the sender, even though the user only intends to send files, not synchronize or delete them.

This behavior is unexpected and potentially dangerous, especially on mobile devices.

Steps to reproduce

1. Send files from Device A (mobile) to Device B using Warpinator.

2. Start sending the same files again from Device A to Device B.

3. Stop the transfer by denying/canceling the request.

4. On Device A, delete or move some of the previously sent files.

5. Send files again from Device A to Device B.

6. Warpinator shows the warning:

   “Files may be overwritten.”

7. Accept the request.

Bugous result

Files that no longer exist on Device A are deleted from Device B, resulting in data loss.

Impact

• High risk of unintentional data loss
• Especially problematic for mobile usage where interrupted transfers are common
• Behavior is not clearly communicated to the user

Suggested Improvements

• Never delete receiver files by default.
• Add a clear confirmation dialog if deletions are about to occur.
• Treat transfers as copy-only, not synchronization.
• Improve warning message to explicitly mention possible deletions.

Environment

• App: Warpinator 2.0.2+zena / Warpinator for Android1.8.5
• Devices: Mobile → Desktop

Expected behavior

• Warpinator should never delete files on the receiving device unless the user explicitly confirms a delete or synchronization operation.
• Interrupted transfers should not lead to implicit file removal.
• The overwrite warning should not imply deletion of missing files.

Additional information

No response

No source file or test is named. Start by reproducing the interrupted and resumed transfer between mobile and desktop devices, then trace the receiver-side handling of missing sender files and cancellation. Done means a transfer never deletes receiver files without explicit confirmation, with regression coverage for the reported sequence.