Search Issue Tracker
Fixed
Votes
6
Found in [Package]
56e5c49289402898806927c1783d265f4989b9cc
Issue ID
1256610
Regression
No
[InputSystem][Android] Touch.isInProgress gets stuck when multiple touches are applied to touchscreen quickly
Steps to reproduce:
1. Select scene "TestScene"
2. Build & Run on Android
3. Select "Touchsceen" from device list at the top
4. See that if you tap, information about touches appears on screen
5. Now tap it with 5+ fingers at once, do it several times, wiggle around
6. Most of the time it will result in touches getting stuck (they're not cleared from the list)
Expected result: isInProgress should get set to FALSE resulting in touches getting cleared from the list of activeTouches
Actual result: isInProgress gets stuck on TRUE and touches are never cleared from the list of activeTouches
Reproducible with:
Xiaomi Mi Note 2 (Mi Note 2), OS: 6.0.1
Sony Xperia Z4 Tablet (SGP771), OS: 6.0.1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- Crash on EnumerateDisabledKeywordsInVariantsArray or UNITY_XXH32 when rapidly saving ShaderGraph or VFXGraph changes
Add comment