RDP for iOS Onscreen Keyboard not populating after closing

Anonymous
2024-07-08T14:20:10+00:00

EDIT 9/13/24: This issue is still present with the newest update to 10.6. We've deployed an alternative solution since, so I'm not really paying much attention to this. I hope they fix this soon, since the update that broke this ironically fixed hardware keyboards.

We have a number of iPads with the latest version of iPadOS and the Microsoft RDP app that have a weird error. These are remotely managed iPads loaded with a few apps, but we primarily use the RDP app on these. I understand that usually these issues fall under Apple Support, but the thing is, this issue is isolated to the RDP app itself. No other app gives me the same issue.

Upon closing and reopening the app, I can log in just fine. The keyboard opens as intended, and I'm able to proceed. Once inside, I'm able to use the keyboard a few times for various apps, but when I close it, sometimes it refuses to reopen. This persists even through locking the session, when prompted to re-enter my credentials to log in via the app itself. The keyboard doesn't appear at all.

I've also tried disabling Bluetooth and enabling the "Show Onscreen Keyboard" option under Accessibility > Touch > AssistiveTouch. I've also enabled AssistiveTouch. No changes.

For a visual representation, see the GIF below. Pulling up the search bar, the keyboard works fine. However, in RDP, I tap the username and password field several times. You can see the AutoFill bubble pop up for half a second towards the end.

At this point, I'm at a loss. I do have full control over this iPad and can wipe it, but ironically I've done this and seen no changes in behavior. I'm thinking it may be an issue with the app. Has anyone seen this before?

TL;DR:

  • Keyboard won't populate in RDP app, works elsewhere fine
  • Turned on "Show Onscreen Keyboard" in AssistiveTouch
  • Turned off Bluetooth
  • Reinstalled RDP app
  • Issue clears after restarting app temporarily, error persists after closing keyboard
  • Error is inconsistent, sometimes keyboard works longer
Windows Server Remote and virtual desktops Remote desktop clients

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

8 answers

Sort by: Most helpful
  1. Anonymous
    2024-10-02T12:34:42+00:00

    We have 2 iPad 11 Pros, and recently upgraded one of them to IOS 18 for iPad. After the upgrade, we are no longer able to access the onscreen keyboard within the RD Client app. When in the app, tapping the keyboard icon turns the icon from white to black and the app change bar at the bottom from black to white, but no keyboard pops up. Tried restarting. No patches available from either MS or Apple. Our other iPad 11 Pro, which still runs IOS 17 works fine.

    3 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-12-19T21:06:40+00:00

    Wondering if this issue was ever solved. If not, will have to look at alternatives for remote access from iPad..onscreen keyboard takes up too much real estate to see sufficient detail on far screen.

    Rod Martin

    0 comments No comments
  3. Anonymous
    2025-01-29T15:42:19+00:00

    Wondering if this issue was ever solved. If not, will have to look at alternatives for remote access from iPad..onscreen keyboard takes up too much real estate to see sufficient detail on far screen.

    Rod Martin

    Hi Rod,

    Unfortunately I never found a fix. Even despite updating our RDP app to the now (terribly named) Windows app, I'm still seeing the same issue. We ended up using a proprietary app that comes with our Remote Application Server that uses RDP itself. Notably, I still see issues but the onscreen keyboard works consistently within it so we've moved to that. Not as good as the Windows app, but it actually works in comparison.

    I'll be raising a ticket with Microsoft support and seeing if they'll do anything about this, but knowing them, I'm not optimistic. If they come back with any information that works, I'll update it here.

    0 comments No comments