Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.58f1
6000.0.38f1
6000.1.0b7
6000.2.0a2
Issue ID
UUM-97712
Regression
No
[Android][iOS] The keyboard closes and re-opens when consecutive input fields are selected
Reproduction steps:
1. Open the attached “IN-95075“ project
2. Build and Run the Android Player
3. In the Player, tap on each input field
4. Observe the Player
Expected result: The keyboard remains open between clicks
Actual result: The keyboard briefly closes and re-opens when another input field is selected
Reproducible with: 2022.3.58f1, 6000.0.38f1, 6000.1.0b7, 6000.2.0a4
Reproducible environments: macOS 15.3 (M3 Max)
Not reproducible environments: No other environments tested
Reproducible with these devices:
VLNQA00591 - samsung Galaxy S23 (SM-S911B), CPU: Snapdragon 8 Gen 2 (SM8550), GPU: Adreno 740, OS: 14
VLNQA00372 - Galaxy S21 5G (SM-G991U), CPU: Snapdragon 888, GPU: Adreno 660, OS: 12
VLNQA00336 - HUAWEI Y6p (MED-LX9N), CPU: MediaTek MT6762R, GPU: PowerVR Rogue GE8320, OS: 10
VLNQA00626 - iPhone 16 (MYE73QN/A), CPU: Apple A18 Pro, GPU: Apple designed, OS: 18.0.1
Note: On Android the whole keyboard re-opens but on iOS, it’s just the input section of the keyboard
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
- Scene View has an inverted Game View window when changing from Game View to Scene View on a specific project
- An error is thrown when one TreeView root element is dragged and held over a parent element but is dropped between the elements
- Text Object position shifts when selecting multiple Text Objects and expanding the Extra Settings in the Inspector
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.