André Sanscartier

Hi, and thank you very much.

The details you provided, especially the screen recording and your answers, were exactly what we needed to look into this.

Since we don't have a BLIKVM device on our side, we can't reproduce your exact setup, but we're confident we've identified the cause. On a host that uses a self-signed certificate, the app was validating the certificate in a way that could block the whole app for several seconds while it waited on the network, which is what you experienced as a freeze. On top of that, the BLIKVM login form is rendered slightly after the page loads, so autofill sometimes ran before the fields existed and left them empty.

We've made a fix for both parts. The certificate check no longer blocks the app, so it stays responsive even with a self-signed certificate. Autofill now waits for the login fields to appear before filling them.

Because we can't test BLIKVM directly, we'll also carefully verify that this change doesn't affect autofill or behavior on other websites before it ships. The fix is done and under review on our side, and it will be included in an upcoming release. We'll follow up here once it's available.

Thanks again for the thorough report and for your patience.

Hi again, and thanks, your description already tells us a lot (it freezes during the autofill, the whole app locks up, and it's specific to BLIKVM). A few targeted follow-ups would let us pinpoint it, since we can't reproduce it here.

The questions are grouped by priority:

🔴 Essential are the ones that matter most

🟡 Preferable help a lot

🟢 Good to know are bonus context

Answer whatever you can. No need to cover everything.

🔴 Essential

1. When the app is frozen, is there a "Filling" spinner/overlay shown on top of the screen (a dimmed overlay with a loading indicator)? This single detail is the most helpful.

2. Does the app recover on its own if you wait ~30–60 s, or do you have to force-close and reopen it?

3. Just before it freezes, do you actually see the BLIKVM login box with the Username/Password fields (even briefly / partly filled), or does it lock up right as the login box is appearing?

4. Is "Auto Submit" (auto-press the Login button) enabled for this entry? And Test A: turn Auto Submit OFF (keep Auto Fill on) : does it still freeze?

5. Test B: turn Auto Fill OFF, then just browse to the BLIKVM login page in RDM and type manually : does everything work normally (no freeze)?

6. A short screen recording of the freeze happening : extremely valuable.

7. RDM for iOS version, iOS version, and device model (e.g. RDM 2025.x, iPhone 15, iOS 18.5).

🟡 Preferable

8. Is two-factor authentication (one-time code) enabled on your BLIKVM login?

9. Test C: leave Auto Fill on but trigger it manually (the key/autofill button) instead of automatically on load : same freeze or not?

10. If you can enable diagnostic logging (Settings → Logs/Diagnostics), reproduce the freeze, and share the log : it shows us exactly where it hangs.

11. The BLIKVM version on the login screen (the green "BliKVM Matrix" badge) and your BLIKVM model.

12. In the entry, are the form/field IDs auto-detected or entered manually? If manual, what are the Form / Username / Password / Submit values?

🟢 Good to know

13. Does it freeze every time, or only sometimes?

14. How is BLIKVM reached ? https:// or http://, IP or hostname ? and is it a self-signed certificate?

15. Does the same BLIKVM autofill work in RDM on another platform (Windows/Android/Mac), or iOS only?

Thanks, this will help us investigate. We can't reproduce it on our side yet, so your answers are what will let us move forward.

Best regards,

Hi,

We have identified the issue and are working on a fix, which will be released shortly.

We will keep you updated on the availability of the new version.

Best regards,

Hi,

We are unable to reproduce your issue and would like to review the log of what happens when the problem occurs.

Could you please provide us with the log from the time of the connection at verbose level 2?

This can be configured in the SSH session.

Regards,

Hi,

Just to let you know that we are waiting on our Lab team to configure a setup similar to yours.

Since last week, we have been undergoing a major reorganization of our offices, which is causing some delays.

Sorry for the inconvenience.

Regards,

Hi,

Thank you for letting us know about this issue. We will investigate and attempt to reproduce your situation. We will get back to you as soon as possible.

Regards,

Hello Carl,

Everything has been tested on Android and iOS, and it works as expected. With a shared data source, it is possible to configure an after-login script on desktop and use it on mobile.

Please advise the user to use this workaround until it becomes possible to configure it directly on mobile.

Additionally, please provide us with feedback when it becomes available.

Best regards,

Hi Carl,

Yes, are we indeed talking about SSH terminal "After login scripts"? Because a similar feature is possible with RDP sessions.

Best regards,

Hi,

Mice are not yet supported in SSH sessions. However, with a long press, you should be able to select and perform your copy-paste operations.

We will add your request to our to-do list and get back to you when we have a scheduled timeline for this feature.

At the moment, we are unable to provide a time frame.

Best regards,

Hi,

In your previous messages, you mentioned that by switching keyboards, you were able to work around the issue. Is that still the case?  

On our side, we could try again to reproduce your problem, but we are running out of ideas.  

Is Gboard still the one that seems to be causing the problem?

Best regards,

Hi,

Have you noticed any improvement in the situation with the latest version of the application?

Best regards,

Hi,

We still haven't been able to reproduce your issue, but we are about to release a new version of the application, hopefully by next week. Although your issue is not specifically addressed in this update, could you let us know if it makes any difference on your side?

Best regards,

Hi,

Apologies for the delay.

We are unable to reproduce the issue on our end.

Could your password contain any non-ASCII characters?

This might help us identify the source of the problem.

Best regards,

Hi,

Sorry that your issue seems to be getting more complex. We will investigate again at the beginning of next week and get back to you.

Best regards,

Hi,

We have some questions.

For which specific issue do you need this option?

What device and type of keyboard (physical or virtual) are you using? 

We could implement an alternative method for sending characters, but we would like to understand the problem you are facing.

Best regards,

Hi,

Your request will be submitted to our technical service for RDP sessions, and we will get back to you as soon as possible.

Best regards,

Hi,

Your screenshot appears to be from RDM-Windows. Is your question in the context of using our mobile or desktop application.

Best regards,

Hi,

Could you please provide us with the versions of your IPad OS and RDM iOS? Just to ensure we conduct the right tests.

Best regards,

Hi,

Please disregard the previous message. We have moved your message to the correct forum.

Best regards,

Thank you for notifying us of the issue. We will investigate and get back to you as soon as possible.

However, we must point out that you are not on the correct forum. For better follow-up, it would be preferable to submit your request on the correct forum, as we were informed by the Mac team, and we only handle iOS and Android.

The specific forum for RDM iOS is https://forum.devolutions.net/product/rdm-ios

Thank you for your understanding.

Best regards,

Hi,

Sorry for the delay. This issue has been added to our to-do list. We will keep you informed as soon as we can provide a time frame.

Regards,

Hi,

Thank you for bringing this issue to our attention. We will attempt to reproduce it and get back to you as soon as possible.

Regards,

Hello,

Sorry for the long delay. After several attempts, something is preventing OpenNote from working correctly through RDM. We have come to the decision to abandon the implementation of your request.

Best Regards,

Hi Kilian,

Just to inform you, we will soon be connecting to your environment with the information you have provided.

We are approaching your request on our to-do list.

Thank you again for your cooperation.

Best regards,

Hi,

When you mention 'this specific device’ do you mean a particular Android device and that it works with other Android devices, or are you referring to a specific server where the problem occurs?

From our side, we are unable to reproduce this behavior.

Additionally, has there been an OS update on your Pixel 7 recently, besides RDM Android?

Best regards,