Sync reports “There was nothing to do” despite transfers and permission errors; remote deletions are silently skipped

[scr4bble]

What version of Round Sync are you using (About → App version)?

Current master branch:

bda00f8d0162acb30a343982c54e3426d2824c15

What is your Android version, phone model, and manufacturer?

• Android 16
• Samsung Galaxy S25

Steps to reproduce

1. Configure an SFTP remote.
2. Configure a Crypt remote wrapping the SFTP remote.
3. Create a Sync local to remote task:
   • Local path: /storage/emulated/0
   • Remote path: a directory inside the Crypt remote
4. Run the task and let it finish.
5. Delete or move a local file, for example from the Download directory.
6. Run the task again.

Actual behavior

Round Sync reports:

There was nothing to do

However, the remote file that no longer exists locally is not deleted.

Logcat shows that rclone cannot read Android-protected directories:

Android/data - failed to open directory "Android/data": permission denied
Android/obb - failed to open directory "Android/obb": permission denied

Because the source scan contains errors, rclone correctly skips the destination deletion phase. However, Round Sync does not clearly report this to the user.

There is also another incorrect result:

1. Add a new local file, for example by taking a photo.
2. Run the task again.
3. The new file is successfully transferred to the remote.
4. Round Sync still reports:

There was nothing to do

The task may display a non-zero error count while running, but the final notification or status still indicates success or says that there was nothing to do.

The configured rclone log directory does not contain the relevant permission or deletion errors. It only contains unrelated startup messages such as:

Setting --local-no-set-modtime "true" from environment variable RCLONE_LOCAL_NO_SET_MODTIME="true"

Expected behavior

Round Sync should:

1. Clearly report that the task completed with errors.
2. Show or persist the underlying rclone errors.
3. Explain that destination deletions were skipped because the source could not be fully scanned.
4. Report transferred files when files were actually transferred.
5. Not show There was nothing to do when transfers or errors occurred.

Summary

• File transfers still work.
• Errors are not transparently exposed to the user.
• Destination deletions are skipped because of source read errors, but this is not reported.
• The final task status incorrectly says There was nothing to do even when files were transferred.
• The final task status also incorrectly says There was nothing to do when errors occurred.