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
- Camera.current returns null when Camera.targetTexture is set to null in OnPostRender
- Crash on BaseHierarchyProperty::Next when opening a specific project
- Shader Compilation for projects with lots of Shaders can be slow (i.e. VFX Graph asset heavy projects)
- The Editor hangs when opening a project that uses local packages and Version Control
- Area Light is culled when Camera Frustrum is outside the lights range
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).