Syncing via removable drives fails when drive is removed too soon
A volunteer who was testing syncing via removable drives found that if they removed the removable drive from the sending device too soon, the file was empty (0 bytes) and the import failed with "Error importing data" on the receiving device.
We already knew this was possible, but I'm opening a ticket for it as it's been seen in the wild.
We may be able to improve how we handle this, for example by showing a more specific error message if the file is empty, or by adding a delay on the sender side before reporting that the write is complete, to allow more time for the data to be written to the drive.