Search Issue Tracker
Fixed
Fixed in 2021.3.30f1, 2022.3.7f1, 2023.1.7f1, 2023.2.0b2, 2023.3.0a1, 7000.0.0a1
Votes
0
Found in
2021.3.26f1
2022.3.0f1
2023.1.0b19
2023.2.0a16
2023.3.0a1
7000.0.0a1
Issue ID
UUM-37652
Regression
No
[Android] Clicks on the "hidden zone" remain blocked when TouchScreenKeyboard is active
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Build And Run on an Android device
4. Open the Android LogCat window and make sure it’s connected to the Android device
5. In Player click the “hidden zone” which is highlighted in the hiddenZone.jpg
6. In the Android LogCat window search for “RELEASED TEXT FIELD REGION CLICK“
7. Observe that every time you tap the “hidden zone“, a similar message to “RELEASED TEXT FIELD REGION CLICK random: 64264“ appears in the Android LogCat
8. In Player click the button with the text “OPEN/CLOSE“
9. Tap on “hidden zone“
10. Observe the LogCat
Expected result: When TouchScreenKeyboard is active, the “hidden zone” does not block clicks and a message similar to “RELEASED TEXT FIELD REGION CLICK random: 64264“ is seen in the Android LogCat
Actual result: Nothing similar to this message “RELEASED TEXT FIELD REGION CLICK random: 64264“ appears in Android LogCat when TouchScreenKeyboard is active
Reproducible with: 2021.3.26f1, 2022.3.0f1, 2023.1.0b19, 2023.2.0a16
Reproducible with devices:
VLNQA00332, Samsung Galaxy XCover4 (SM-G390F), Android 9, CPU: Exynos 7 Quad 7570, GPU: Mali-T720
VLNQA00325, Samsung Galaxy Note10 (SM-N970F), Android 12, CPU: NOT FOUND, GPU: Mali-G76
VLNQA00318, Oneplus OnePlus 7 Pro (GM1913), Android 11, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00231, Samsung Galaxy A5(2017) (SM-A520F), Android 8.0.0, CPU: Exynos 7 Octa 7880, GPU: Mali-T830
VLNQA00231, Huawei HUAWEI Mate 20 Pro (LYA-L29), Android 9, CPU: HiSilicon Kirin 980, GPU: Mali-G76
Testing environment: Windows 10 Enterprise 21H2
Note:
- The user provided more info about this issue in this forum thread: [https://forum.unity.com/threads/touchscreenkeyboard-hideinput-triggers-numerous-errors-breaks-functions-in-current-android-unity.1303749/#post-9012400|https://forum.unity.com/threads/touchscreenkeyboard-hideinput-triggers-numerous-errors-breaks-functions-in-current-android-unity.1303749/#post-9012400]
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 2021.3.30f1):
For Unity Editor 2021.3 version, when you test fixes on the project, you need to set consumesOutsideTouches to false before calling TouchScreenKeyboard.Open("") as shown below.
TouchScreenKeyboard.Android.consumesOutsideTouches = false;
keyboard = TouchScreenKeyboard.Open("");
This is because for Unity Editor 2021 version, the default value of consumesOutsideTouches is true, and the default value of consumesOutsideTouches is false on the 2022 or higher version
Check the default values in the links below
*https://docs.unity3d.com/2021.3/Documentation/ScriptReference/TouchScreenKeyboard.Android-consumesOutsideTouches.html
*https://docs.unity3d.com/2022.1/Documentation/ScriptReference/TouchScreenKeyboard.Android-consumesOutsideTouches.html