Search Issue Tracker
Fixed in 2020.3.42f1
Fixed in 2020.3.X, 2021.3.X, 2022.1.X, 2022.2.X, 2023.1.X, 2023.1.0a19
Votes
1
Found in
2020.3.40f1
2021.3.11f1
2022.1.19f1
2022.2.0b10
2023.1.0a13
Issue ID
UUM-16292
Regression
No
[Android] Keyboard gets hidden when the input field area is clicked and TouchScreenKeyboard.hideInput is set to true
How to reproduce:
1. Open the user’s attached “1359628_hide_input” project
2. Build And Run the “SampleScene” Scene on Android
3. Click the “Open” button to view the keyboard
4. Click the input field area slightly above the keyboard
Expected result: Keyboard doesn’t get closed
Actual result: Keyboard gets closed
Reproducible with: 2020.3.40f1, 2021.3.11f1, 2022.1.19f1, 2022.2.0b10, 2023.1.0a13
Reproduced on: macOS 12.5 (Intel)
Reproducible with devices:
VLNQA00472 - Samsung Galaxy A52 (SM-A525F), CPU: Snapdragon 720G (SM7125), GPU: Adreno 618, OS: 12
VLNQA00414 - Galaxy Note10+ 5G (SM-N976V), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 9
VLNQA00409 - Galaxy Z Fold3 5G (SM-F926B), CPU: Snapdragon 888, GPU: Adreno 660, OS: 11
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Group Selection title text size is smaller in renaming than the actual font size
- Rich Text is not correctly highlighted when searching through Debug Logs in the Console window
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
Resolution Note (fix version 2023.1):
Fixed in 2023.1.0a19
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0b16
Resolution Note (fix version 2022.1):
Fixed in 2022.1.23f1
Resolution Note (fix version 2021.3):
Fixed in 2021.3.14f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.42f1