Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X, 2021.1.X, 2021.2.X
Votes
20
Found in
2020.2.0a19
2020.3
2020.3.13f1
2021.1
2021.2
2022.1
Issue ID
1347370
Regression
Yes
[Android] Using TouchScreenKeyboard.Open with a non-empty placeholder multiple times causes the app to crash
Reproduction steps:
1. Open the attached user's project "KeyboardTest.zip"
2. Build for Android with Development Build Enabled
3. Press the "Show Keyboard" button
4. Repeat step 3 until the app crashes
Expected result: App crashes when opening keyboard with non-empty placeholder
Actual result: App crashes when opening keyboard with non-empty placeholder
Reproduces on: 2020.2.0a19, 2020.3.14f1, 2021.1.14f1, 2021.2.0b3, 2022.1.0a1
Does not reproduce on: 2019.4.29f1, 2020.2.0a18
Reproducible with these devices:
N/A, Samsung Galaxy S9 (SM-G960F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00002, Samsung S5 Neo LTE (SM-G903F), Android 6.0.1, CPU: Exynos 7 Octa 7580, GPU: Mali-T720
VLNQA00318, Oneplus 7Pro (GM1913), Android 10, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00231, Huawei HUAWEI Mate 20 Pro (LYA-L29), Android 9, CPU: HiSilicon Kirin 980, GPU: Mali-G76
VLNQA00366, Samsung Galaxy Z Fold2 5G (SM-F916U), Android 10, CPU: Snapdragon 865 SM8250, GPU: Adreno (TM) 650
Notes:
-Crash is reproducible with Mono and IL2CPP Scripting backends
-In 2022.1.0a1 only the Samsung S5 Neo reproduces the crash if IL2CPP is selected
-Application does not crash if the Placeholder is empty
-In 2021.1.0a10 and above the crash is no longer reproducible on iOS
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
- UpdateRendererBonudingVolumes process takes more time when disabled Renderers are used
- "ArgumentNullException: Value cannot be null" error is thrown when selecting a Visual Element with a custom Render Texture set as a background
- Changes are not saved when changing Styles' orders in the UI Builder
- “InvalidOperationException: Not enough space in output buffer (need 24, has 0)” error is thrown when using NativeList.GetVertices()
- High CPU usage when Spline Evaluate functions are used
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a6
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0b9
Resolution Note (fix version 2021.1):
Fixed in 2021.1.20f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.17f1