You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Caused by: java.lang.NullPointerException
at papa.Choreographers$isInChoreographerFrameMessage$2.invoke(Choreographers.kt:13)
at papa.Choreographers$isInChoreographerFrameMessage$2.invoke(Choreographers.kt:12)
at papa.MainThreadMessageScopedLazy.getValue(MainThreadMessageScopedLazy.kt:17)
at papa.Choreographers.isInChoreographerFrameMessage(Choreographers.kt:12)
at papa.Choreographers.isInChoreographerFrame(Choreographers.kt:31)
at papa.Choreographers.postOnFrameRendered(Choreographers.kt:51)
at papa.InteractionEngine$RealRunningInteraction.finish(InteractionRuleClient.kt:167)
at papa.OnEventScope$DefaultImpls.recordSingleFrameInteraction(InteractionRuleClient.kt:279)
This is happening because not all main thread code actually runs from dequeuing a message. For instance, touch event handling is done independant of any main thread message dispatching, i.e. in between two messages:
at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:4147)
at android.view.ViewRootImpl$AsyncInputStage.forward(ViewRootImpl.java:4307)
at android.view.ViewRootImpl$ImeInputStage.onFinishedInputEvent(ViewRootImpl.java:4468)
at android.view.inputmethod.InputMethodManager$PendingEvent.run(InputMethodManager.java:2435)
at android.view.inputmethod.InputMethodManager.invokeFinishedInputEventCallback(InputMethodManager.java:1998)
at android.view.inputmethod.InputMethodManager.finishedInputEvent(InputMethodManager.java:1989)
at android.view.inputmethod.InputMethodManager$ImeInputEventSender.onInputEventFinished(InputMethodManager.java:2412)
at android.view.InputEventSender.dispatchInputEventFinished(InputEventSender.java:141)
at android.os.MessageQueue.nativePollOnce(Native Method)
at android.os.MessageQueue.next(MessageQueue.java:325)
at android.os.Looper.loop(Looper.java:142)
The text was updated successfully, but these errors were encountered:
Crash:
This is happening because not all main thread code actually runs from dequeuing a message. For instance, touch event handling is done independant of any main thread message dispatching, i.e. in between two messages:
The text was updated successfully, but these errors were encountered: