Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4
2018.4
2018.4.12f1
2019.2
2019.3
2020.1
Issue ID
1194594
Regression
No
Input phase "Moved" is not registered when Thread is sleeping
Steps to reproduce:
1. Open and build supplied project
2. Press the button, then drag across the screen
Expected: 'Began', 'Moved', 'Ended' movement events are registered and shown in the text field
Actual: only 'Began' and 'Ended' movement events are registered
Reproduced in: 2017.4.34f1, 2018.4.12f1, 2019.2.12f1, 2019.3.0b10, 2020.1.0a12
Reproduced on:
VLNQA00257, Sony Xperia XZ Premium (G8141), Android 9, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00070, Lenovo Lenovo PHAB2 Pro (Lenovo PB2-690M), Android 6.0.1, CPU: Snapdragon 617 MSM8952, GPU: Adreno (TM) 510
VLNQA00022, Xiaomi Redmi Note 3 (Redmi Note 3), Android 5.1.1, CPU: Snapdragon 617 MSM8952, GPU: Adreno (TM) 510
VLNQA00146, Htc 10 (HTC 10), Android 7.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
VLNQA00127, Lge Nexus 5X (Nexus 5X), Android 8.0.0, CPU: Snapdragon 808, GPU: Adreno (TM) 418
VLNQA00099, Google Pixel XL (Pixel XL), Android 9, CPU: Snapdragon 821 MSM8996 Pro, GPU: Adreno (TM) 530
iPad 7th generation (iOS 13.1)
Mono and IL2CPP , .NET 2.0 and 4.x
Reproducible on Win Standalone
Not reproducible on Switch
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
- Fixing Message Loss in UMPE During Domain Reload
- The Editor freezes when ScheduleReadOnly of IJobParallelForTransform with dependency is used
- Text is truncated in the Inspector when the display scale is set to 150%
- CancellationTokenSource(<timeout>) has incorrect cancellation status when used in WebGL Player
- VFX property value names are cut off when properties with 'Arc' are viewed in the VFX Blackboard
Resolution Note:
The legacy input system (everything in UnityEngine.Input class) only supports a single Touch.Phase change per frame, because Thread.Sleep pauses the execution of a frame it's expected that only that last event will be returned.
This issue will be resolved in the new input system where we'll have callbacks for all touch event.