[iOS] sFTP Broken in 2026.1.1.1

More context: prior to 2026.1.1.1, I was connecting to / as my home directory which would put me at the root of the file system. Now it just spins trying to load.

If I do /opt as the home directory it will put me in /opt when connecting and so forth.

If I remove / or /opt as the home directory and put / as the starting directory it puts me in root's home folder (/root).

I need to be able to free browser the file system and having to edit the connection for every path is not practical.

In summary, using / as the home directory is no longer working.

Hello,

Thank you for contacting us regarding this matter.

Could you please confirm whether you have experienced the issue on a PC as well? Additionally, could you let me know what your data source is?

Do you have any logs available? Does the issue affect all entries or only SFTP? Are the other entries working correctly?

Best regards,

Hello,

Thank you for contacting us regarding this matter.

Could you please confirm whether you have experienced the issue on a PC as well? Additionally, could you let me know what your data source is?

Do you have any logs available? Does the issue affect all entries or only SFTP? Are the other entries working correctly?

Best regards,

@Tommy Sanders

I have only experienced this on iOS. Data source is devolutions personal hub. I'll see if I can pull logs. When trying from iOS Termius and Windows WinSCP, works just fine.

I tried connecting again and viewed the log of RDM and it said I was connecting to X.x.x.118:22 when I was really connecting to X.x.x.129:22.

after viewing the log, it wouldn't properly close as it was still partially open. See attached screenshot. At this point, RDM was non responsive to any navigation.

i went to the Home Screen and then back in to RDM where I sat at the splash screen for about 5 seconds before RDM crashed. I was able to reproduce this multiple times.

Hi,

You mentioned that prior to iOS 2026.1.1.1, sFTP was working. Could you please tap on the hamburger icon at the top left of the screen, select About, then choose Update History, and send us an image of your update history?

Screenshot as requested.

Hi,

We were able to reproduce the issue, or at least what we believe is causing it. We have created a ticket to address it.
We will keep you informed once it is fixed and ready for release.

Best Regards,

Was the fix included in yesterday's release of 2026.1.2.2?

Hi,

No, a fix has not been found yet.

Best Regards,