Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.3.X
Votes
0
Found in
2018.4
2019.4.0f1
2020.2
Issue ID
1257101
Regression
No
[WebGL] [Input System] Touch input is ignored on WebGL builds when using new Input System and running the build on mobile device
Reproduction steps:
1. Open the attached project ("case_1257101-WebGLMobileTouch.zip")
2. Switch build target to WebGL
3. Make a build and host in somewhere on a server
4. Run the build inside a mobile device
5. Try interacting with the cube (touch/swipe)
Expected result: Touch input is recognized and the cube can be rotated around
Actual result: Touch input is ignored and the cube does not rotate
Reproducible with: 2018.4.25f1, 2019.4.4f1, 2020.1.0b16, 2020.2.0a18
Reproducible with package (Input System) versions: 0.9.0, 1.0.0
Notes:
1, The issue does not reproduce on the mobile devices when using the old input system
2. The issue does not reproduce when running the build on PCs
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
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
- [Mono] Crash on SystemNative_ReadDirR() when building for IOS/Android on a macOS machine
Resolution Note (fix version 2021.1):
Touch events were working with the new input system, but the current control scheme wasn't switching properly so PlayerInput wasn't routing those events. This fix prioritizes the Touchscreen device so that on mobile those events get routed.
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.28f1