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
- Visible instance buffer returns 0 for every instance when using BatchDrawCommandIndirect on Adreno devices with Vulkan API
- [Android][Vulkan] Native crash in AndroidVulkanVideo::ProcessFrame and AndroidVulkanVideo::Context::~Context() when switching screens
- Screen brightness is not set to a default value when Screen.brightness is set to a negative value
- macOS app window title is not localized when built from generated Xcode project
- Unity Hub doesn't preserve the changed Channel when manually restarting the Hub
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).