New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MixedRealityInputModule throws KeyNotFoundException from OnPointerUp #7989
Comments
Here are the relevant sequences of callstacks from the Unity log, starting with the first unhandled exception. Some frames are unavailable due to .NET Native compilation and inlining. KeyNotFoundException: Arg_KeyNotFound KeyNotFoundException: Arg_KeyNotFound Mixed Reality Controller Right was never registered with the Input Manager! (Filename: C:\buildslave\unity\build\Runtime/Export/Debug.bindings.h Line: 45) KeyNotFoundException: Arg_KeyNotFound Mixed Reality Controller Right was never registered with the Input Manager! (Filename: C:\buildslave\unity\build\Runtime/Export/Debug.bindings.h Line: 45) NullReferenceException: |
Sorry to be commenting on an old and closed issue but I believe I'm running into this, or a very similar issue, on MRTK v2.4.0:
|
Do we have an update if this is resolved? Or any other workaround? |
Describe the bug
In Remote Assist, we sometimes see a KeyNotFoundException thrown from MixedRealityInputModule.OnPointerUp. After this exception is thrown, input stops working for the remainder of the app session due to unhandled NullReferenceExceptions being thrown from
To reproduce
Reproduction is difficult, but I believe it is necessary to be holding a pressed hand state with a far-interaction pointer when the hand goes out of scope (OnSourceLost).
Expected behavior
There should not be KeyNotFoundExceptions thrown from this callstack.
Your setup (please complete the following information)
Target platform (please complete the following information)
Additional context
Based on my debugging, I believe that the following sequence of events are happening:
2/ The MixedRealityInputModule's OnSourceLost handler handles the event first, and removes the pointer data from its Dictionary
The text was updated successfully, but these errors were encountered: