Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.57f1
6000.2.3f1
6000.3.0b1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-117108
Regression
No
Touch inputs stops registering after 20-100 touches in the Device Simulator view
Steps to Reproduce:
1. Open the attached “IN-113970” project
2. Open the “Combat” Scene (Assets/Scenes/GameScenes/Combat.unity)
3. Enter Play Mode
4. Open the Simulator view
5. In the Simulator view, tap repeatedly until game stops taking inputs (Tap on non-interactable in-game objects to prevent the game from stopping)
6. Observe the Console window for touch feedback
Expected results: Touch input is always registered and logged
Actual result: after 20-100 touches, the input is no longer registered
Reproducible with: 2023.3.0a5, 6000.0.57f1, 6000.2.3f1, 6000.3.0b1
Reproducible environments: Windows 11 (by reporter), Windows 10
Not reproducible environments: macOS 15.6.1 (M3 Max)
Reproducible with these devices:
By reporter - Samsung Galaxy A53, CPU: Exynos 1280, GPU: Mali-G68
Not reproducible with these devices:
VLNQA00641 - Google Pixel 9 (Pixel 9), CPU: -, GPU: Mali-G715, OS: 15
VLNQA00372 - Galaxy S21 5G (SM-G991U), CPU: Snapdragon 888, GPU: Adreno 660, OS: 12
Note: After the input stops registering, switch to Game view and then back to Simulator view to unfreeze it
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.