Unreachable SMB share does not cause an error message

[Sogolumbo]

• I have read the above note

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

2.5.6
Rclone Version:
1.68.0-extract

What is your Android version, phone model and manufacturer?

Android Version 13, Samsung Galaxy S9, LineageOS

Which steps are required to reproduce this issue?

Example:

1. Create a SMB remote, and a task
2. Make sure that the remote is unreachable
3. Enable Logging
4. Trigger the task manually
5. Round Sync takes a long time to time out
6. Round Sync creates an error in the log file:
   2026-01-16 11:59:10 - 2026/01/16 10:59:10 ERROR : : error listing: couldn't connect SMB: dial tcp xxx.xxx.xxx.xxx:445: i/o timeout
7. Round Sync states in the "Log" section of the app that the sync was successfull, there was nothing to do. This is wrong

What is your configuration (rclone.conf)?

Probably not needed.

Does the same issue also occur when using the same configuration on a PC or in Termux?

Not tested since it's probably not needed.

[Sogolumbo]

Looking briefly into the code I found this possible problem which may or may not be related to this bug:
The enum value FAILURE_REASON.RCLONE_ERROR is defined and an error message is defined. But there is no occurrence in the code where this value is assigned to any variable.

[Sogolumbo]

Another thing which doesn't make sense to me:
In the doWork function, SyncWorker.kt, line 123 it seems to me like success of the operation is decided upon before the operation has finished (handleTask())
In handleSync(), which is called by handleTask(), it seems like rsync command line output is collected and parsed (line 191).

If my intuition is right, the error messages will appear inside SyncWorker.statusObject.mErrorList.

This bug could probably be fixed by checking the length of statusObject.mErrorList before defining the Result inside doWork().
If the length of the error list bigger than zero the result should be failure.

Since I don't know kotlin and don't have the IDE installed I won't try to fix this myself. I hope my analysis helps anybody trying to fix this issue.