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
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
- Entities Hierarchy window allows Cyclic nesting and throws an “ArgumentException: Cyclic nesting detected” error when dragging a Prefab onto the same Prefab in the Entities Hierarchy
- EnterPlayModeOptions doesn't take effect if user manually modifies m_EnterPlayModeOptionsEnabled to 0
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).