iOS Outlook App - repeatedly closes on-screen keyboard (whilst typing!) and “attached” keyboard

Anonymous
2020-04-07T09:36:03+00:00

I’ve been using iOS Outlook for a while on an iPad Pro. Apart from its quirky style, which is a bit of a steep learning curve, even coming from over a decade of using Outlook for Windows, it has a major keyboard bug. It closes the on-screen keyboard (whilst typing!) and even an “attached” physical keyboard is deactivated during typing.

This manifests itself thus: you can type two or three words, then the keyboard on the screen disappears. So you reload it, type a bit more, and it closes again.

It does exactly the same thing for at attached physical keyboard.

If I switch to the iOS Mail app (native Apple), I have no keyboard issues, either on screen or physical. The same is true for all other apps on the device.

This strongly supports the fact that the iOS Outlook app has a keyboard bug. I’ve reported this to my IT department, who say nobody else says it does this. I have seen online similar iOS keyboard issues with Microsoft apps in the recent past, so I suspect this is a known bug.

Solution is not to use iOS Outlook for typing. :-)

Anybody know a ‘fix’ for the app please? I’ve reinstalled it, to no benefit.

Outlook | Outlook for mobile | Outlook for iOS | For home

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.

0 comments No comments

88 answers

Sort by: Most helpful
  1. Anonymous
    2020-06-16T08:24:06+00:00

    Got the same issue here, very annoying thinking about using a different Mail app just for that reason.

    my env.:

    • ipad 12.9 (2020)
    • apple super keyboard floating
    • IOS 13.4.1
    • 512 GB space (370 GB free)

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-05-31T15:16:47+00:00

    I also have this problem with my O365 account. There's just one additional IMAP account connected to iOS Outlook, so it's not due to Gmail in my case (that's in its own app). I'm running iOS 13.5 on a 2020 iPhone SE. I just composed a short email and by the time it was done my nerves were totally shot with the keyboard disappearing close to 10 times during those 3 sentences.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-05-22T14:34:20+00:00

    Ah.  I don’t use that, so I don’t know.  But I wouldn’t be surprised if the problem/fix is similar; i.e., Outlook is auto-saving a draft as you’re typing, which is fine if it keeps the draft locally, but it’s also trying to simultaneously sync that draft back to some system folder, and that’s what is pulling you out of composing whatever email you are composing.  Good luck.

    My fix above fixed it for me.  There was a rogue “drafts” folder that I didn’t need on the system (in my case, Gmail) that was syncing with Outlook mid-composing and that sync shut down the composing.  I deleted the folder on the system side (i.e., on Gmail) and it has worked flawlessly ever since on multiple devices (ipad, iphone).

    Hi - no, I've had no luck either, despite loads of communications from M$ asking me to try various 'fixes'. None of which have worked. The only solution is to not use it, but as my employer requires me to do so for encrypted emails, I sometimes find myself replying to emails, then giving up as I can't type more than a few characters before the keyboard evaporates into thin air.

    Can you explain this some more? I just see one Drafts folder in my Gmail. Where did the rogue folder come from, how did you know it was causing the issue, and how did you remove it?

    Nevermind - I just re-read your original post. My issue is with an O365 email account (haven’t noticed it when composing an email with my Gmail account...but I use it far less)...

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-05-22T14:25:06+00:00

    My fix above fixed it for me.  There was a rogue “drafts” folder that I didn’t need on the system (in my case, Gmail) that was syncing with Outlook mid-composing and that sync shut down the composing.  I deleted the folder on the system side (i.e., on Gmail) and it has worked flawlessly ever since on multiple devices (ipad, iphone).

    Hi - no, I've had no luck either, despite loads of communications from M$ asking me to try various 'fixes'. None of which have worked. The only solution is to not use it, but as my employer requires me to do so for encrypted emails, I sometimes find myself replying to emails, then giving up as I can't type more than a few characters before the keyboard evaporates into thin air.

    Can you explain this some more? I just see one Drafts folder in my Gmail. Where did the rogue folder come from, how did you know it was causing the issue, and how did you remove it?

    Nevermind - I just re-read your original post. My issue is with an O365 email account (haven’t noticed it when composing an email with my Gmail account...but I use it far less)...

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2020-05-22T13:59:07+00:00

    My fix above fixed it for me.  There was a rogue “drafts” folder that I didn’t need on the system (in my case, Gmail) that was syncing with Outlook mid-composing and that sync shut down the composing.  I deleted the folder on the system side (i.e., on Gmail) and it has worked flawlessly ever since on multiple devices (ipad, iphone).

    Hi - no, I've had no luck either, despite loads of communications from M$ asking me to try various 'fixes'. None of which have worked. The only solution is to not use it, but as my employer requires me to do so for encrypted emails, I sometimes find myself replying to emails, then giving up as I can't type more than a few characters before the keyboard evaporates into thin air.

    Can you explain this some more? I just see one Drafts folder in my Gmail. Where did the rogue folder come from, how did you know it was causing the issue, and how did you remove it?

    Was this answer helpful?

    0 comments No comments