Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.21f1
2023.2.13f1
2023.3.0b10
Issue ID
UUM-65849
Regression
No
[Android][Input][Text] TextField.touchScreenKeyboard sometimes loses input
Steps to reproduce:
1. Open the “AndroidFocus” project
2. Build And Run the project on the device
3. Press the Populate Value button and observe the number on the right of the “Focusable” text, then press the Reset Value button
4. Repeat step 3 for 20 times
Expected result: The value is always 26
Actual result: Sometimes the value is lower, and some of the characters are lost
Reproducible with: 2022.2.3f1, 2022.3.21f1, 2023.2.13f1, 2023.3.0b10
Could not test with: 2021.3.36f1-2022.2.2f1 (TextField doesn’t have the touchScreenKeyboard method)
Testing environment: macOS Sonoma 14.3.1 (Intel), Windows 11 (by user)
Not reproducible on: No other environment tested
Reproducible with these devices:
VLNQA00017 - Huawei Nexus 6P (Nexus 6P), CPU: Snapdragon 810 MSM8994, GPU: Adreno 430, OS: 8.0.0
VLNQA00409 - Galaxy Z Fold3 5G (SM-F926B), CPU: Snapdragon 888, GPU: Adreno 660, OS: 11
VLNQA00334 - Xiaomi Mi A3 (Mi A3), CPU: Snapdragon 665 SM6125, GPU: Adreno 610, OS: 11 (takes a lot of tries to reproduce)
VLNQA00526 - samsung Galaxy A12 (SM-A125F), CPU: Mediatek MT6765 Helio P35 (12nm), GPU: PowerVR Rogue GE8320, OS: 12
Not reproducible with these devices:
VLNQA00536 - iPad 8th Gen (WiFi) (MYL92HC/A), CPU: Apple A12 Bionic, OS: 15.2
VLNQA00394 - iPhone 13 mini (MLK23ET/A), CPU: Apple A15 Bionic, OS: 16.2
Notes:
- Depending on the device, for some, the number can be 24 or lower, but more often it’s 25
- Sometimes it’s easier to reproduce when pressing the Reset Value button in the Player → Home screen (don’t close the Player) → open the app again from where all of the apps are (like App Drawer)
- Not reproducible with iOS or Standalone
- Not a regression as TextField.touchScreenKeyboard method was a new feature
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
- Editor crashes when starting a new game session using Direct3D12 Graphics API
- Play on awake does not work with an audio random container when instantiating a game object
- Play on awake does not work with an audio random container when loading a scene
- Prefab components are not rendered correctly in the Inspector Window when "HideFlags.HideInInspector" is used
- The "Editor.CreateInspectorGUI" method is being called twice when the Console and the Inspector windows are in the same panel
Resolution Note:
Hi. Thanks for the report. We're aware the touch keyboard on Android is not always responsive but it will require a more comprehensive refactor that we cannot do as part of this bugs fix. This will sometimes yield some missed key presses if they are done too quickly (like using a script).