Search Issue Tracker
Fixed in 2023.2.0a8
Fixed in 2023.2.X, 2023.3.X, 2023.3.0a1
Votes
1
Found in
2022.1.0a15
2022.2.0a1
2023.1.0a1
2023.2.0a1
2023.3.0a3
Issue ID
UUM-3696
Regression
No
[UI Toolkit][Android][Mouse][Touchpad] UI Toolkit is not interactable when using mouse or touchpad
How to reproduce:
1. Connect Mouse or Controller to Android device
2. Build & Run the project
3. Try clicking any Button, Toggle, Input Field, or using other UI in the scene
Expected result: Toggle gets marked, Input Field opens the keyboard, Slider is draggable
Actual result: Nothing happens
Tested with Apple Magic Mouse, PlayStation DualShock 4 Controller
Reproducible: 2022.1.0a15
Tested devices:
Samsung Galaxy S21 Ultra (SM-G998B), Android 11, CPU: Exynos 2100, GPU: Mali-G78
VLNQA00340, Samsung Galaxy Note20 Ultra 5G (SM-N986B), Android 10, CPU: Exynos 990, GPU: Mali-G77
Google Pixel 4, Android 12, CPU: Snapdragon 855 (SM8150), GPU: Adreno (TM) 640
VLNQA00405, Galaxy Z Flip3 5G, CPU: Snapdragon 888, Android: 11, GPU: Adreno 660
iOS - the trackpad isn't supported
Reproducible with Old and New Input Systems
Not reproducible with UGUI, IMGUI
Comments (2)
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
grrava
Jan 01, 2024 15:30
I am getting reports from users that this is still not fixed in 2023.2.4f1
grrava
Nov 13, 2023 18:53
Please backport the fix to 2022.3 - is there a workaround in the meantime?