Search Issue Tracker
By Design
Votes
0
Found in [Package]
preview.4 - 1.0.0
Issue ID
1221108
Regression
No
[Android] UnityEngine.InputSystem.EnhancedTouch.Touch Value Not Initialized when touching the screen
Steps to reproduce:
1. Open User's attached project "Block Quest 2.0.zip"
2. Build it to an Android device
3. When app is opened, press "DESIGNER"
4. Zoom in, Zoom out, Move Around in the Camera
5. Notice the Logcat output errors related to "InputSystem"
Expected results: No errors related to "InputSystem" are displayed in the console
Actual results: InputSystem related errors are displayed in the console
Reproducible with: 2020.1.0a23(preview.5 - 1.0.0)
VLNQA00153, Google Pixel XL (Pixel XL), Android 10, CPU: Snapdragon 821 MSM8996 Pro, GPU: Adreno (TM) 530
VLNQA00024, Xiaomi Mi 5 (MI 5), Android 7.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
VLNQA00315, Samsung Galaxy Note10 (SM-N970U), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
Note: It might take couple of times to reproduce the issue. Unable to test below 2020 due to project braking. The input System package was not present in 2018.4
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
- "Rendering Debugger" displays incorrect overdraw count when using "Unlit/Texture" shader
- Scene and Game views break when the Editor window is snapped with the Microsoft PowerToys
- Materials do not transfer texture when the "Shader" parameter is changed from "Unlit/Texture" to "Universal Render Pipeline/Unlit"
- [Linux][Vulkan] Crash when opening searchable dialog
- The "Shader error in 'AE/Leaves': "Undefined punctual shadow filter algorithm"" error appears when build completes on a specific project
Resolution Note:
User error.
See documentation for Finger.currentTouch:
https://docs.unity3d.com/Packages/com.unity.inputsystem@1.1/api/UnityEngine.InputSystem.EnhancedTouch.Finger.html
Users code doesn't check the "valid" property for the touch and the exception is thrown in cases when the current touch is invalid.
The issue only happens on Android, because the code in question is Android-only (is behind UNITY_ANDROID define).