Search Unity

  1. Looking for a job or to hire someone for a project? Check out the re-opened job forums.
    Dismiss Notice
  2. Good news ✨ We have more Unite Now videos available for you to watch on-demand! Come check them out and ask our experts any questions!
    Dismiss Notice

Keyboard doesn't show up on Android 11 when the input field is hidden

Discussion in 'Android' started by JuliusM, Sep 28, 2020.

  1. JuliusM

    JuliusM

    Unity Technologies

    Joined:
    Apr 17, 2013
    Posts:
    619
    Currently using hide input field option prevents the on-screen keyboard from showing up on devices with Android 11. We are making the quick workaround by changing how the input field is hidden. After the workaround is implemented, the input field as well as the text in it will be transparent. That is not an ideal solution, but it's the fastest and safest fix for now.
    We are planning to make the fix in all currently supported Unity versions.
    The issue can be tracked here https://issuetracker.unity3d.com/is...-with-hide-mobile-input-checked-on-android-11

    Edit: The fix was made in these Unity versions: 2018.4.29f1, 2019.4.13f1, 2020.1.11f1 and 2020.2.0b10.
     
    Last edited: Nov 4, 2020
    jhocking-bundlar likes this.
  2. justin_bling

    justin_bling

    Joined:
    Oct 24, 2019
    Posts:
    2
    Is there an ETA on this workaround?
     
  3. andersemil

    andersemil

    Joined:
    Feb 2, 2015
    Posts:
    81
  4. Tomas1856

    Tomas1856

    Unity Technologies

    Joined:
    Sep 21, 2012
    Posts:
    2,489
  5. JuliusM

    JuliusM

    Unity Technologies

    Joined:
    Apr 17, 2013
    Posts:
    619
    The issue gets marked as resolved in the issue tracker when the QA verifies it. That means there can still be a period of time when the issue is marked resolved, but the version which contains the fix is not yet released.

    As Tomas has said, for 2018LTS the fix will be available with 2018.4.29f1. The fix was also made in 2019.4.13f1, 2020.1.11f1 and 2020.2.0b10.
     
    andersemil likes this.
  6. andersemil

    andersemil

    Joined:
    Feb 2, 2015
    Posts:
    81
    My bad, sorry, I misread the release notes of 2018.4.28 ... it lists it as a known issue, I read it as a fix.
     
  7. leedan_unity

    leedan_unity

    Joined:
    Jun 17, 2019
    Posts:
    5
    I'm going to challenge the acceptability of the workaround Unity has used to circumvent the issue.

    A) The input field is not completely hidden. The following images demonstrate underlining and highlighting still being shown just above the keyboard with the 'hidden' input field.
    https://drive.google.com/file/d/1HVq88wVnpTuktaJ3_quXc_WEZxyo0xha/view?usp=sharing
    https://drive.google.com/file/d/1HSlk1-7ewW5l99tani5v8jSvBxnjGlXp/view?usp=sharing
    https://drive.google.com/file/d/1HYC0OfKnZtBSlXo0uGpI89893E0icNy8/view?usp=sharing

    B) The 'hidden' input field still blocks raycasts, preventing touches from propagating to the intended target. This has caused a significant number of issues for clients, as they are unable to interact with the app as expected. The effect is minimal with short strings, but long inputs can block touches over a significant portion of the screen. This can be seen in second image above as it prevents the buttons from being pressable.
     
  8. JuliusM

    JuliusM

    Unity Technologies

    Joined:
    Apr 17, 2013
    Posts:
    619
    Which Unity version do you use and on which device do you see this behavior? Does it happen on other devices as well? From what I remember, it should not be possible to interact with the game elements while the keyboard is open, so these issues would not happen. There was one device that was working differently (I can't remember which one now), but everything else that our QA tested behaved the same. Maybe this behavior is present only in Unity 2019 and up.
     
  9. leedan_unity

    leedan_unity

    Joined:
    Jun 17, 2019
    Posts:
    5
    We're currently using 2019.4.15f1. The visible artifacts are present on my Samsung Galaxy S8, and I suspect the keyboard I'm using (Fleksy) may be partially to blame for the visible highlighting.

    Historically (on Android) the first tap on the screen when the keyboard is active will not interact with onscreen elements, but it does serve to dismiss the keyboard. This two tap process is an unpleasant user experience issue on it's own, but at least in this scenario, a user trying to tap one of the buttons in the previous photo may have to tap twice, but they would be able to tap the button and perform the action. The new hidden input field blocks touches from dismissing the keyboard as our users have come to expect, and so they would have to tap elsewhere on the screen (outside of the area blocked by the transparent text field) to dismiss the keyboard, before being able to tap the button.
     
  10. leedan_unity

    leedan_unity

    Joined:
    Jun 17, 2019
    Posts:
    5
    Still haven't heard anything back on this, and we continue to receive customer complaints. Is this issue going to be addressed?
     
  11. RobinopdeBeek

    RobinopdeBeek

    Joined:
    Jan 17, 2018
    Posts:
    13
    I agree with @leedan_unity. I have been waiting for a fix for this for a long long time now. The 'fix' where simply not rendering the input field is terrible! It's still super messy in 2020.1.16f1 and simply unusable. It blocks raycasts and you can still select stuff in the invisible input field. I have attached a screenshot of the issue.
    https://drive.google.com/file/d/1HzBuSUmU4MQnavZLEHT09tlrWylUwvzq/view?usp=sharing

    Isn't an input field one of the most basic things you can have in an app? Why is it so hard to get this right?

    Edit: The screenshot is from a Pixel 2.

    Edit: Also tested it on 2020.2.1 but has the same issue (Pixel 2). Here another screenshot:
    https://drive.google.com/file/d/17dVXJq0DtdIoheSRH7r80qc2v6irLxpA/view?usp=sharing
     
    Last edited: Jan 14, 2021
  12. RobinopdeBeek

    RobinopdeBeek

    Joined:
    Jan 17, 2018
    Posts:
    13
unityunity