Search Issue Tracker

Fixed in 2022.1.X

Fixed in 2019.4.X, 2020.3.X, 2021.1.X, 2021.2.X

Votes

8

Found in

Issue ID

1360514

Regression

Yes

[UWP] HoloLens TouchScreenKeyboard closes ~4 seconds after focusing TMP input field

Universal Windows Platform

-

When selecting an input field in HoloLens2, the Keyboard will open but then automatically closes after ~4 seconds.

Steps:
1. Open attached project
2. Build for UWP and run on HoloLens2 (or HL2 emulator)
3. Use the on-screen keyboard to enter text into the input field
4. Close the Keyboard
5. Select the input field again to re-open the keyboard
6. Wait about 5 seconds

Expected: Keyboard remains open
Actual: Keyboard automatically closes after ~4 seconds

This bug is related to this issue: https://issuetracker.unity3d.com/issues/uwp-xbox-onscreenkeyboard-is-immediately-closed-when-selecting-inputfield. The fix (workaround WinRT bug with InputField::Show()) introduced a race-condition that's now causing this problem.

It's also related this this other issue: https://issuetracker.unity3d.com/issues/hololens-2-set-selection-throws-argumentoutofrangeexception. The unhanded exception is a factor in triggering this bug, but the root issue is a race-condition.

  1. Resolution Note (fix version 2022.1):

    The fix for TMP ArgumentOutOrRange exception: https://issuetracker.unity3d.com/issues/hololens-2-set-selection-throws-argumentoutofrangeexception will also address this issue. The unhanded exception is one of factors leading to this problem. However, a separate fix for the root problem (race condition) is also being made.

Log in to vote on this issue

Comments (10)

  1. Martin-Aunovis

    Dec 18, 2023 11:20

    Issue is not fixed. Using Unity 2022.3.7f1 and it still happens.

  2. alexanderlarsen

    Jul 06, 2022 07:27

    Same problem here in Unity 2019 and 2020 (tested up to 2020.3.33).

  3. unity_8R3gaxreN6dMTA

    Nov 25, 2021 09:17

    I've been doing this:

    void Input(){

    if(keyboard.active == false){
    keyboard.active =true;
    }
    }

  4. yeongjuBae

    Nov 16, 2021 06:34

    Hello~
    I'm using 2021.1.12. Can't you fix it?
    Currently, the version with this issue resolved is not available because the package manager has not been called normally.

  5. Spoon92

    Sep 15, 2021 08:34

    Into which version of 2020.3.X will this fix be shipped?
    And thanks for the quick fixing of the issue. :ThumbsUp:

  6. AvatarJoe

    Sep 14, 2021 21:14

    I'm extremely appreciative of the quick turn around, thank you for addressing this.

  7. timke

    Sep 07, 2021 22:59

    I working to backport the fix to 2019 LTS as quickly as possible.

  8. Spoon92

    Aug 30, 2021 18:16

    We witness a similar issue in Unity 2020.3.16f1

  9. AvatarJoe

    Aug 25, 2021 18:47

    Hey guys, if possible can we get this fixed in Unity 2019.4 first? Most of the people experiencing this issue will be working with the HoloLens 2 and relying on Legacy XR which is in 2019.4. Much appreciated.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues