Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.3.13f1
2019.4.0f1
Issue ID
1260753
Regression
Yes
[Android] Can't relocate the caret in Input Fields when Hide Mobile Input option is being used
Repro steps:
1. Create a new project
2. Add a regular Input Field
3. Enable "Hide Mobile Input"
4. Build and Run on Android
5. Touch the Input field
6. Enter some text and try to move the caret to the middle of the text
Actual: Caret can't be moved
Reproducible with: 2019.3.13f1, 2019.4.3f1, 2020.1.0b14, 2020.2.0a17
Doesn't reproduce with: 2019.3.12f1
Tested and reproduced on these devices:
VLNQA00013, Samsung Galaxy S6 edge+ (SM-G928F), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
VLNQA00001, Google Pixel 2 (Pixel 2), Android 11, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
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
Didn't reproduce on:
iPhone 11 (iOS 13.5)
-
artoonie
Jun 22, 2022 19:28
I'm not sure how this is marked Won't Fix - is the idea that this isn't a bug? The resolution note is confusing.
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
Resolution Note (2020.2.X):
In Unity 2019.3.12f1 (where according to the description of this case) the issue was not reproducible, the caret indeed could be moved in the input field, however by doing so the keyboard gets closed anyway and to show it again, the user has to tap outside of the input field and onto the input field again. This resets the caret position at the end of the text essentially providing no benefits from the ability to move the caret.