This still happens on version 2.5.4. I had two remotes, one plain WebDAV and the other a crypt remote called "backup" on that WebDAV host. When I created a new Alias remote pointing to the WebDAV remote and named it "backup", a green toast said Remote created succesfully while the crypt remote had disappeared from the list (and nothing replaced it), then a red toast said Error retrieving remote backup.
While the WebDAV remote can still be browsed from within Round Sync, it has disappeared from the Content Provider in Android Files, where it now says 0 remotes available. Restarting the app didn't fix this. So it seems something really breaks behind the scenes when creating a remote with the name of an existing remote.
This still happens on version 2.5.4. I had two remotes, one plain WebDAV and the other a crypt remote called "backup" on that WebDAV host. When I created a new Alias remote pointing to the WebDAV remote and named it "backup", a green toast said Remote created succesfully while the crypt remote had disappeared from the list (and nothing replaced it), then a red toast said Error retrieving remote backup.
While the WebDAV remote can still be browsed from within Round Sync, it has disappeared from the Content Provider in Android Files, where it now says 0 remotes available. Restarting the app didn't fix this. So it seems something really breaks behind the scenes when creating a remote with the name of an existing remote.