Error retrieving remote

[Erz3]

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

2.5.4

What is your Android version, phone model and manufacturer?

Android 11, Realme X2

Which steps are required to reproduce this issue?

Example:

1. Create a Crypt remote
2. Upload something with a task in that remote
3. Delete that remote
4. Create another remote with the same name, the same password and salt (all the same).
5. Popup is show with: "Error retrieving remote [remote_name]"

Please also enable rclone logging (Settings > Logging > Log Rclone errors). You're going to need the log for the last question.

Does it really needed? RS is working with default settings.

What is your configuration (rclone.conf)?

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

[Erz3]

Ok, error is because I failed to set up correctly the remote route. However, error is show over and over again and I can't delete wrong remotes because Round Sync is not showing them in the list.

[BRKsays]

You have to edit the rclone config file and remove the wrong remote. I did the same when I faced the issue.

[Erz3]

You have to edit the rclone config file and remove the wrong remote. I did the same when I faced the issue.

does I need root in my device?

Rclone should show wrong remotes in the main menu.

[BRKsays]

does I need root in my device?

Maybe not if you can get to the rclone.conf directly on Android filesystem.

The way I did it is I exported config from settings, unpacked the zip, edited the rclone config found in the zip, zipped it again, then imported it in Round Sync via settings.

Rclone should show wrong remotes in the main menu.

Raise a ticket for that as a feature request/usability issue.

[Erz3]

The way I did it is I exported config from settings, unpacked the zip, edited the rclone config found in the zip, zipped it again, then imported it in Round Sync via settings.

I haven't got time to try this, at the moment. However, you have convinced me, It sound a good solution that should work, so I will close this issue.

Raise a ticket for that as a feature request/usability issue.

Of course.