Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2018.4.X, 2019.4.X, 2020.1.X, 2020.2.X
Votes
42
Found in
2018.4
2018.4.23f1
2019.4
2020.1
2020.2
Issue ID
1258071
Regression
No
[Android] Keyboard doesn't show up when trying to input text in an Input Field with Hide Mobile Input checked on Android 11
Repro steps:
1. Create a new project and create an Input Field (reproduced with regular and TMPro Input Fields)
2. Build and Run on an Android device with Android 11
3. Press on the Input field
Actual: The keyboard doesn't show up
Reproducible with: 2018.4.24f1, 2019.4.2f1, 2020.1.0b14, 2020.2.0a16
Tested and reproduced on these devices:
VLNQA00001, Google Pixel 2 (Pixel 2), Android 11, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
Didn't reproduce on:
VLNQA00013, Samsung Galaxy S6 edge+ (SM-G928F), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
VLNQA00078, Motorola Nexus 6 (Nexus 6), Android 7.1.1, CPU: Snapdragon 805 APQ8084AB, GPU: Adreno (TM) 420
VLNQA00225, Qualcomm (SDM845 for arm64), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00128, Samsung Galaxy Note8 (SM-N950F), Android 9, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
VLNQA00317, Vivo V1924A (V1924A), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00294, Oppo Reno Z 中国版 (PCDM10), Android 9, CPU: Mediatek MT6779 Helio P90, GPU: PowerVR Rogue GM9446
Oneplus OnePlus 6 (ONEPLUS A6003), Android 10, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
MaestroDev
Oct 12, 2020 18:23
Issue is still present in Unity 2019.3. Would love to get this fix out of "In Review" for Unity 2019 and fixed.
andersemil
Oct 08, 2020 07:39
This affects our app atm on 2018.4. Our workaround until Unity releases a patch is to enable mobile input on all InputFields if running Android API 30
VennSamson
Oct 05, 2020 22:37
We are addressing this issue in our product with a small patch that addresses the issue partially, but would prefer if the original functionality were restored to this component when it interacts with Android 11. Please address this soon.
RobinopdeBeek
Oct 05, 2020 08:30
Is there an estimate as to when / which version this will be fixed?
Jishnu_M
Sep 29, 2020 05:26
Is this issue is fixed?
leedan_johnson
Sep 24, 2020 19:42
We've started getting complaints from users because of this issue. Needs fixed right away.
BearHugMark
Sep 10, 2020 16:44
This is a live issue for us and we really need this resolved. It currently causes a soft lock because the player has to input their name before they can continue further in the game.
joshleeoutplay
Sep 10, 2020 14:03
Still getting this issue on Android 11 release, on both TextMeshPro and GUILayout TextFields.
n00levoy
Aug 10, 2020 13:59
Sorry for being misleading, keyboard works fine when you select fields with unchecked "hide mobile input", but when you focus on a field which mobile input should be hidden, it just breaks and keyboard stops appearing even in first case.
eladfein
Aug 07, 2020 20:01
The issue still happens on Android 11 beta 3