Search Issue Tracker
Fixed in 2018.3.5f1
Fixed in 2017.4.X, 2018.3.X
Votes
2
Found in
2017.4.6f1
Issue ID
1102448
Regression
No
[Android] Keyboard doesn't open when an InputField is touched with API Level 28
Repro steps:
1. Open attached project
2. Make sure Target API Level is set to "Automatic (highest installed)"
3. Build and Run on Android
4. Touch the Input Field
Expected: Keyboard is opened up when the InputField is touched
Actual: The keyboard doesn't open up
Reproducible with: 2017.4.15f1, 2018.2.16f1, 2018.3.0b11, 2019.1.0a10
DUT:
Reproduced on:
VLNQA00124, Google Pixel 2 XL (Pixel 2 XL), Android 9, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
Fixed in: 2019.1.0a12
Backported to: 2017.4.26f1, 2018.3.5f1
Comments (36)
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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
StylishName
Mar 27, 2022 13:08
Great.. This Fixed my Error.
mentalup
Oct 09, 2019 11:58
It still happens on some devices with 2019.6.1f
micbigtree
Sep 13, 2019 13:31
hi guys has this been fixed? getting the same thing text strip and 'ok' button bit no keyboard, unless i click on the input strip. sony xperia
rankornfeld
Jun 25, 2019 17:22
I think this issue is back with 2018.4.2f1
Works on 2018.3.13f1 but when I try to build with the latest LTS version it fails.
LordScottWarren
May 20, 2019 14:03
Why has there been not been fixed? Does anyone have a work around?
magnusfox
May 17, 2019 10:08
This is not fixed. I can confirm it's still present in 2019.1.2f0 on a Samsung Galaxy S8 (Android 9.0) with Swiftkey used.
gothic0327
May 12, 2019 12:50
This is good with Gboard (google keyboard) and SwiftKey, but it is not work with Samsung keyboard.
Unity version: 2018.4
UnityDeveloperPune
Apr 23, 2019 11:13
The issue is also noticed in Unity 5.6.4p4.
Will there be a fix for lower versions of Unity ?
aklgupta
Jan 29, 2019 13:26
Can this is backported to earlier version? Or some other workaround be provided officially for those with projects in earlier versions?
dominykasm
Jan 09, 2019 10:47
This will probably be fixed in 2018.3 too. Gonna update on this.