Search Issue Tracker
By Design
Votes
0
Found in [Package]
Issue ID
1310053
Regression
No
Multiple Touchscreen devices references/names on Android is not consistent
Some Android devices appear to have more than one Touchscreen available at the start of a scene, and which of them it picks as Touchscreen.current is not always consistent.
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
- Prefab override popup is cropped/positioned incorrectly when more than one display is used and a higher display Scale is set
- Opening a dropdown on a small screen results in its instant closing when mouse cursor is pressed where the dropdown is going to be opened
- Only "ArgumentNullException: Value cannot be null" is displayed instead of all the actual errors when opening a project with numerous compilation errors
- MultiColumnListView and MultiColumnTreeView do not change selection on first input when focus is set by code
- SerializedProperty.DataEquals is returning false when SerializedProperty.EqualContents return true
Resolution Note:
Relying on order of discovery won't be robust. Device-specific information supplied by the platform should be available from the capabilities field in InputDeviceDescription (can be accessed via InputDevice.description).