Search Issue Tracker
Duplicate
Votes
0
Found in
2019.4
2020.3.23f1
2020.3.32f1
2021.3
2022.1
2022.2
Issue ID
1421624
Regression
Yes
[TMP][Android] Keyboard doesn't show up when TouchScreenKeyboard.Open() function is called on an Android device
How to reproduce:
1. Open the user's attached "Ludia-Keyboard.zip" project
2. Build and Run the "SampleScene" on an Android device
3. In the Build press the "ShowKeyboard" button
Expected results: The keyboard shows up
Actual results: No keyboard shows up, only the navigation bar appears
Reproducible with: 3.0.6 (2019.4.38f1, 2020.3.23f1, 2021.3.1f1, 2022.1.0f1, 2022.2.0a11), 4.0.0-pre.1 (2022.1.0f1, 2022.2.0a11)
Not reproducible with: 3.0.6 (2020.3.22f1)
Reproducible with:
VLNQA00391, Xiaomi Redmi 9A (M2006C3LG), Android 10, CPU: MediaTek Helio G25 (MT6762G), GPU: PowerVR Rogue GE8320
----------, Oppo Reno Z 中国版 (PCDM10), Android 11, CPU: NOT FOUND, GPU: PowerVR Rogue GM9446
VLNQA00335, Samsung Galaxy S20+ 5G (SM-G986B), Android 10, CPU: Exynos 990, GPU: Mali-G77
Not reproducible with:
VLNQA00286, Meizu Pro 5 (PRO 5), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00310 - iPad Pro 12.9", 13.4.1 iOS
VLNQA00392 - iPad (9th generation), 15.0 iOS
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
Add comment