Hello Jump Desktop Support Team,

I am experiencing several issues with Jump Desktop. I have tried to isolate each problem and would like to report them separately below.

1. Pressing the "i" Key Incorrectly Sends Ctrl Modifier Events in Fluid Sessions

The most serious issue is a very specific keyboard input problem when connecting to a Windows computer using Jump Desktop Fluid.

Environment

Client: Jump Desktop for iOS
Jump Desktop iOS version: 10.15.31
Connection type: Fluid
Host: Windows
Windows edition: Windows 11 (non-Pro)
Windows RDP: Disabled / not being used
Jump Desktop Connect: Latest available version
Keyboard layout: Turkish Q
iPhone keyboard language/layout: Turkish

The problem occurs only with the "i" key.

When I press i through Jump Desktop:

The character i is entered correctly.
At the same time, both Left Ctrl and Right Ctrl are briefly triggered on the Windows host.
The Ctrl keys immediately release.
This happens consistently every time I press i.
No other letter key behaves this way.

For example:

u → normal
i → i + Left Ctrl + Right Ctrl
o → normal
j → normal
k → normal
l → normal

I tested essentially all other letter keys and could reproduce the issue only with i.

The Alt key is also incorrectly sent

There is another important detail regarding the modifier keys.

Initially, when I pressed i, Alt was also being triggered together with Ctrl.

I then changed the following Jump Desktop setting:

Ignore Left Alt → Enabled

After enabling this option, the Alt event stopped appearing, but the Left Ctrl and Right Ctrl events still occur every time I press i.

So the Alt issue appears to be suppressed by the Jump Desktop setting, rather than the underlying keyboard event being correct.

The current behavior is therefore:

Without "Ignore Left Alt":

i → i + Ctrl + Ctrl + Alt

With "Ignore Left Alt":

i → i + Ctrl + Ctrl

The setting "Left Alt Is Right Alt" is disabled.

Windows On-Screen Keyboard test

I used the Windows built-in On-Screen Keyboard to observe exactly which modifier keys are being received.

When I press i through Jump Desktop's iOS on-screen keyboard, Windows' On-Screen Keyboard shows both Left Ctrl and Right Ctrl becoming active briefly.

However, if I press i directly using the Windows On-Screen Keyboard itself, neither Ctrl key is triggered.

This is an important comparison because the Windows keyboard layout itself does not generate these Ctrl events for the i key.

Physical keyboard is not the cause

I also tested with a physical hardware keyboard connected to the iPhone.

The same problem occurs:

Physical keyboard → Jump Desktop Fluid → Windows

Pressing i still briefly activates both Ctrl keys.

The issue can also be reproduced using only Jump Desktop's built-in iOS on-screen keyboard, without any physical keyboard connected.

Therefore, the problem is not specific to the physical keyboard or the iPhone's touch keyboard.

Ctrl state test

I also tested whether this could be caused by a stuck Ctrl modifier.

If I manually activate Ctrl using the Windows On-Screen Keyboard:

Click Ctrl once → Ctrl becomes active.
Click Ctrl again → Ctrl becomes inactive.

Ctrl also behaves normally when activated from the iOS keyboard or a physical keyboard.

However, when Ctrl is completely inactive, pressing i through Jump Desktop immediately causes both Ctrl indicators to flash.

Therefore, this does not appear to be a permanently stuck Ctrl key.

I also tested the situation where Ctrl was manually activated. In that case, the Ctrl state could remain active, which made me suspect that Jump Desktop may have an issue with modifier key state handling.

Browser behavior

This is also visible in Chrome and Edge.

When I press i, the character is entered, but the browser also behaves as if a Ctrl-related shortcut has been pressed. For example, the browser UI/three-dot menu can become focused.

This appears to be consistent with Windows receiving additional Ctrl key events together with the i key.

TeamViewer comparison

I performed an important A/B test using the exact same Windows computer and the exact same keyboard.

When I connect to the same Windows computer using TeamViewer:

i works normally.
No Ctrl key is triggered.
The problem does not occur.

Therefore, the Windows computer, keyboard, Turkish keyboard layout, and applications are the same. The main difference is the remote desktop software.

Additional configuration tests

I have already checked/tested:

Windows Turkish Q keyboard layout
iOS Turkish keyboard layout
Physical keyboard settings
Jump Desktop Macros → disabled
"Left Alt Is Right Alt" → disabled
"Ignore Left Alt" → enabled
Restarted Jump Desktop after changing settings
Windows On-Screen Keyboard
Physical keyboard
iOS on-screen keyboard
Multiple other letter keys
TeamViewer

None of these resolved the Ctrl issue.

Summary of the keyboard problem

The issue can essentially be reproduced as:

Jump Desktop Fluid → press i → Windows receives i + Left Ctrl + Right Ctrl (+ Alt if Ignore Left Alt is disabled)

while:

Windows On-Screen Keyboard → press i → only i

and:

TeamViewer → press i → only i

The same problem also occurs when connecting from my MacBook using Jump Desktop Fluid.

Because the problem is isolated specifically to the i key and does not occur with TeamViewer on the same Windows machine, I strongly suspect a keyboard event translation/mapping issue in Jump Desktop Fluid or Jump Desktop Connect.

2. Touch/Click Offset When Using an External Monitor with iPhone

I also have another issue when using Jump Desktop on my iPhone while an external monitor is connected to the iPhone.

In this configuration, sometimes the touch/click position does not exactly match the visual position of the UI element.

For example, I may touch directly on a button, but Jump Desktop registers the click slightly to the left or slightly above the actual touch position.

The important detail is that:

It does not affect the entire screen.
It only happens in certain areas of the screen.
Other areas work correctly.
The offset is relatively small, but it is enough to cause me to miss buttons and click next to them.

This appears to be related to coordinate mapping/scaling when using an external display.

It would be useful if you could investigate whether there is a known issue with touch coordinate mapping, scaling, or display resolution when Jump Desktop is used on an iPhone with an external monitor.

3. Deleted RDP Connection Keeps Reappearing

I have one more issue with the device/connection list.

There is an RDP connection entry in my Jump Desktop device list that I cannot permanently delete.

I have deleted this entry dozens of times (approximately 50 times).

However, every time I completely close and reopen the Jump Desktop application, the same RDP entry appears again.

The behavior is:

Open Jump Desktop.
Delete the RDP entry.
The entry disappears.
Close Jump Desktop completely.
Reopen Jump Desktop.
The same RDP entry appears again.

I have repeated this process many times, but the entry continues to return.

I am not using RDP for my current connection. I am using Fluid, and RDP is disabled on the Windows host.

This makes me suspect that the deleted RDP entry may be getting restored from some kind of synchronization, cached configuration, or account/device database.

Could you please investigate why this particular RDP entry cannot be permanently deleted?

Overall

These three issues appear to be independent:

Fluid keyboard input: i incorrectly generates Ctrl/Alt modifier events.
External monitor: occasional touch/click coordinate offset on certain parts of the screen.
Device list: a deleted RDP entry repeatedly reappears after restarting the application.

The first issue is particularly reproducible and can be demonstrated using the Windows On-Screen Keyboard, so I would be happy to provide screenshots, screen recordings, diagnostic logs, or any other information that would help your developers reproduce it.

Please let me know if you need any additional diagnostic information from either the iOS client or the Windows Jump Desktop Connect application.

Thank you for your help.

Multiple Bugs: Incorrect Keyboard Input, External Display Touch Offset, and Undeletable RDP Entry