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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
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).