Search Issue Tracker
Fixed in 1.2.0
Votes
0
Found in [Package]
1.1.0-pre.6
Issue ID
1357664
Regression
No
[InputSystem] Touchscreens Multi-Touch doesn't work when using a custom InputActionAsset
How to reproduce it:
1. Open the user's attached project "inputsystem-multitouch-bug.zip"
2. Build and Run it on device
3. Click on "Broken InputActionAsset" button
4. Click with two fingers on green area
5. Observe yellow dots
Expected result: There 2 yellow dots appear
Actual result: There only 1 yellow dot appears
Reproducible with: 1.1.0-pre.6 (2019.4.30f1, 2020.3.17f1, 2021.1.19f1, 2021.2.0b10, 2022.1.0a7)
Reproducible on:
VLNQA00122, Samsung Galaxy S9 (SM-G960F), Android 10, CPU: Snapdragon 855 SM8150, GPU: Mali-G72
VLNQA00331, Huawei P20 lite (ANE-LX1), Android 9, CPU: HiSilicon Kirin 659, GPU: Mali-T830
VLNQA00321, Xiaomi MI 9 (MI 9), Android 10, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00285, Samsung Galaxy J4 Core (SM-J410F), Android 8.1.0, CPU: Snapdragon 425 MSM8917, GPU: Adreno (TM) 308
VLNQA00013 - Galaxy S6 Edge+ (SM-G928F), OS: 7.0.0, CPU: Exynos 7 Octa (7420), GPU: Mali-T760
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
- Symlinks are broken when a package which contains .xcframework + symlinks is added through Unity Package Manager.
- Crash on ApplyMaterialPass when opening a specific scene
- Memory leak when using Native Plugin in Windows IL2CPP Build
- [URP][Tutorial] Universal 3D Sample tutorial issues
- Gradle error: "...Unexpected error during link..." is thrown when building for Android and targeting API Level 34
Resolution Note (fix version 1.2.0):
Fixed in Input System 1.2.0 available in Unity 2019.4 and above
Resolution Note (fix version 1.2.0):
Fixed in Input System 1.2.0 available in Unity 2019.4 and above