Search Issue Tracker
Fixed in 5.3.8
Votes
25
Found in
5.3.5f1
Issue ID
800999
Regression
No
[iOS] "Stale Touch Detected!" error after the game minimizing and re-opening again
To reproduce:
1. Build attached project to iOS and run it
2. Press the "home" button to minimize the project
3. Open it again, and immediately start tapping the screen with multiple fingers
4. In the upper right of the screen, where some errors are shown, there should appear a "Stale touch detected!" error. If it doesn't appear in a few seconds, redo steps 2-4.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
ollyrennardarcticshores
Nov 07, 2017 09:36
Not fixed in 5.5.2, any clues what the workaround is or if it's something that can be put directly into the xcode project?
yoshida_nurve
Aug 30, 2017 02:10
@ANDYJENKINS30
You can see 'Workaround is possible' by mousing over the text "Severity: 3" in this page.
AndyJenkins30
Aug 03, 2017 08:29
This bug should be fixed in Unity versions 5.6.3p3 & 2017.3 - backports to 5.5 & 5.4 aren't going to happen I am afraid.
@ROBERT_231PLAY - Severity 3 stands for "Secondary functionality is broken", not "'Workaround is possible" - did you find this reference in the docs? If you link it here I'll go ahead and change it.
adamt
Feb 10, 2017 17:51
There have been forum threads and bug reports about this since 2009. I submitted a bug report in August of 2016 and received a comment back that the QA team had successfully reproduced the issue, but could not tell me when a fix would be available (thanks...).
It's sort of insane, really. It clutters up log files and provides no meaningful guidance to developers about where/why it's happening, and Unity refuses to do anything about it. ugh
szu3d
Feb 09, 2017 03:10
stack trace is:
--------------------
Stale touch detected!
0 UnityEngine.Application.CallLogCallback(String, String, LogType, Boolean)
--------------------
or
--------------------
Stale touch detected!
0 System.IComparable`1.CompareTo(T)
--------------------
Unity 5.3.5.P6。
Robert_231Play
Jan 25, 2017 13:57
Severity is set to 3, 'Workaround is possible'.
Can you please provide information about the workaround?
Cheers
russiac
Jan 13, 2017 08:20
please help me....