Devolutions ForumDevolutions Forum

Mobile app is buggy

avatar
titanpro



When I exit and go back in with Wayknow, I just get a black screen (it IS connected). And only one monitor shows as available. Then I use RDP on my laptop to get to the external laptop (so I can see if the laptop is working okay). After that, the popup on Wayknow is black again. When I do see the laptop screen in the app, the screen now shows the primary screen but if I select the second monitor, the popup is just black again.

In summary, it seems starting Wayknow on the lPad is not waking up the remote laptop. And the "..." switch to the second monitor results in a back popup with nothing to select (like going back to the primary monitor).  

Two bugs with similar symptoms.

All Comments (2)

avatar
Richard Markiewicz

Hello

Thanks for the detailed bug report. I'm going to work on reproducing that on my side. In the meantime - can you confirm you are running the latest Wayk Now version on your iPad (2020.1.4)? The easiest way to verify, is to open the App Store and make sure no Wayk Now update is available.

Thanks and kind regards,

Richard Markievicz

avatar
Richard Markiewicz

Hello again

There is a known incompatibility running RDP sessions on the remote machine with an active Wayk Now session. It's documented already here, but to summarize:

  • If you have an active RDP session on the remote machine while you are connected with Wayk Now, minimizing the RDP client may cause the Wayk session to turn black. This is because the RDP client sends a message that causes all remote graphics rendering to stop.
  • The same issue will occur when you disconnect the RDP session (that is; close the RDP window without logging off the remote machine - leaving the RDP session connected but not active). That is for the same reason as above.
  • If you connect to a remote machine that has an RDP session active, you may not see all the physical monitors - the RDP session is simulating a single display connected to the remote machine at a specific resolution.


Can you try again, ensuring that there is no RDP session (active or "idle") on the remote machine?

Thanks and kind regards,

Richard Markievicz