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: Newest
  1. Anonymous
    2020-10-06T14:30:10+00:00

    You have to turn off power saver mode in battery settings.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-10-06T02:15:56+00:00

    I’ve just updayed to iOS 14.01 and I now have the same symptom. Infuriating is an understatement as it jusy took mw 15 minutes to write a 2 minute enail reply.... only happens in The Outlook app as far as I can tell. 

    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.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2020-10-03T14:38:53+00:00

    Exactly the same issue here, iPad Air, latest version, iOS fully updated, problem only occurs in Outlook, no other apps. Outlook is unusable for composing messages.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-09-18T17:40:38+00:00

    Hello,

    i also have this problem. I have just installed office as ive started training and my university has asked me use outlook for email and calender but my keyboard keeps closing after a few characters are typed. This makes it impossible to use on my ipad but i cant use anything else.

    phil

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2020-09-18T08:22:24+00:00

    Yes, very annoying and ruining the use of the Outlook app when using iPad pro as laptop replacement!

    Was this answer helpful?

    0 comments No comments