Search Issue Tracker
Fixed in 1.0.1
Votes
0
Found in [Package]
1.0.0
Issue ID
1258165
Regression
No
[New Input System][Mobile] Touch.tapCount is always 0
Steps to reproduce:
1. Open user's attached project "DeviceSimBugs.zip"
2. Build it to Android
3. Notice "tap count" is always 0
Expected results: tap count changes
Actual results: tap count does not change
Reproducible with: 2019.4.2f1(1.0.0), 2020.1.0b14(1.0.0), 2020.2.0a15(1.0.0)
VLNQA00220, Samsung Galaxy Note9 (SM-N960F), Android 8.1.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00123, Google Pixel 2 XL (Pixel 2 XL), Android R, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00024, Xiaomi Mi 5 (MI 5), Android 7.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
iPhone XR (iOS 13.4.1)
iPhone 8 Plus (iOS 12.0)
iPad Air 2 (iOS 11.0.3)
Unable to test with: 2018.4 due to errors
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on UnityPlayer!profiling::ProfilerManager::DisposeProfilerRecorder+0xa when Player gets relaunched and exited after running for a long amount of time
- [Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
- Root motion is not reapplied when transitioning from an animation without root motion to an animation with root motion
Add comment