Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X
Votes
2
Found in
2018.4
2019.4
2019.4.16f1
2020.1
2020.2
2021.1
2021.2
Issue ID
1305663
Regression
No
[Android] The area just above the pop up keyboard is nonresponsive when Hide Mobile Input setting is used
Repro steps:
1. Create a new project
2. Add an Input Field and check the "Hide mobile input" setting
3. Build and Run on an Android device
4. Press the Input field to open the keyboard
5. Try to close the keyboard by touching the area just above it where the input field preview would appear if "hide mobile input" wouldn't be used
Actual: That area is nonresponsive and doesn't close the keyboard
Expected: The keyboard closes when touching any part of the screen that doesn't belong to the keyboard
Reproducible with: 2018.4.31f1, 2019.4.18f1, 2020.1.17f1, 2020.2.2f1, 2021.1.0b3, 2021.2.0a2
Tested and reproduced on these devices:
VLNQA00013, Samsung Galaxy S6 Edge Plus (SM-G928F), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
VLNQA00331, Huawei P20 lite (ANE-LX1), Android 9, CPU: HiSilicon Kirin 659, GPU: Mali-T830
VLNQA00001, Google Pixel 2 (Pixel 2), Android 11, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00231, Huawei HUAWEI Mate 20 Pro (LYA-L29), Android 9, CPU: HiSilicon Kirin 980, GPU: Mali-G76
VLNQA00078, Motorola Nexus 6 (Nexus 6), Android 7.1.1, CPU: Snapdragon 805 APQ8084AB, GPU: Adreno (TM) 420
Didn't reproduce on:
iPhone 11 (iOS 13.5)
-
RobinopdeBeek
Feb 09, 2021 09:15
Is there any progress on this issue? I've been waiting for the hidden mobile input issue to be fixed for almost 6 months now.
-
RobinopdeBeek
Jan 22, 2021 11:29
To add to the issue: You can also edit text in the invisible inputfield just above the keyboard as if there still is mobile input. Selecting all text in the inputfield will show the selection feedback in the mobile input as well.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2020.3):
Fixed in 2020.3.16f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.30f1