tstpierre
commented
10 years ago I'm getting this regularly on some devices still, even with the latest (1.2.5 currently) jars.
ANR Input dispatching timed out (Waiting because the touched window has not finished processing the input events that were previously delivered to it.) in com.nothingsoftstudios.dlbb/com.unity3d.player.UnityPlayerNativeActivity
I find it very easy to trigger an ANR when running my game and an Impact opens.
I get the following from logcat: I/InputDispatcher( 599): Application is not responding: Window{427d2078 u0 com.example/com.unity3d.player.UnityPlayerNativeActivity}. It has been 6077.1ms since event, 5003.7ms since wait started. Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
I/WindowManager( 599): Input event dispatching timed out sending to com.example/com.unity3d.player.UnityPlayerNativeActivity. Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
What I do to trigger it is simply to swipe my finger across the screen just before the Impact is due to start and let go when the buffering dialogue is shown. Then I do nothing for 6 seconds and I get the ANR dialogue.