Search Issue Tracker
Fixed in 1.0.2
Votes
0
Found in [Package]
56e5c49289402898806927c1783d265f4989b9cc
Issue ID
1256839
Regression
No
[InputSystem] No errors are thrown when trying to use EnhancedTouch when it is disabled
Steps to reproduce:
1. Check 'ReflectDevicePropertiesScript.cs' to see that the "EnhancedTouchSupport.Enable();" line is commented out in OnEnable()
2. Select Scene "TestScene"
3. Build & Run on a device with touchscreen (in this case it's a smartphone)
4. Select "Touchsceen" from device list at the top
5. See that if you tap, information about touches does not apprear on the screen (EnchancedTouch is disabled)
6. Check the logs to see that no errors are thrown
Expected result:
Logs should make it clear that EnhancedTouch is being used but it's disabled (throw exception)
Actual result:
There are no exceptions thrown
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
- “GUIStyle” and “NullReferenceException” errors thrown in the Console when opening Object Field during script compilation
- Reflections are visible on objects without Recursive Rendering when viewed through transparent parts of another object with Recursive Rendering and Alpha Clipping enabled
- Visual artifacts appear when using "clip" method in custom shader and running on GLES
Add comment