OnHandUpdate processes invalid hand

[BCrowderKB]

Describe the bug
OnHandUpdate condition checks don't account for handData.hand == 0

To Reproduce
Steps to reproduce the behavior:

1. Open WebXRInputSystem.cs
2. Add console log above "DisableHandRight();" call
   Debug.Log("Invalid Hand: "+(handData.hand == 0));
3. Make build
4. Enable & Disable your hands via emulator or other means
5. Notice console prints "Invalid Hand: true"

Expected behavior
No update should occur if OnHandUpdate is called with an invalid hand
e.g. adding a guard clause at the beginning of OnHandUpdate: if (handData.hand == 0) return;

Screenshots

Unity info (please complete the following information):

• Editor version: 6000.0.32f1
• WebXR package version: 0.22.1
• WebXR Interactions version: 0.22.0 (with previous hand event fix)
• OpenUPM
• Input System + XR Interaction Toolkit
• Built-in render pipeline

Desktop (please complete the following information):

• Windows 11
• Chrome

Additional context
I noticed a few spots that default to right hand that should probably check for hand == 2.

I found this while trying to debug a fatal input manager "memory out of bounds" error that was infrequently thrown when Exiting VR in my Quest 3.

Also unrelated but in case you didn't see the tracked pose driver bug claims to have been fixed in InputSystem package 1.13.2 https://issuetracker.unity3d.com/issues/gameobject-is-placed-at-position-0-0-0-when-entering-play-mode-if-using-trackedposedriver

[De-Panther]

Thanks.
Was the "memory out of bounds" happened because of this issue?

I found possible places where it could send data with invalid hand and fixing those as well.

And yes, I saw they fixed it, thanks. Got email about it (opened the issue there).

[BCrowderKB]

I think the "memory out of bounds" error is unrelated to this issue, but does relate to the hand input devices (at least in my project). I can't recreate it with your samples so it may be an issue with my setup or caused by the newer versions of the input system / another package.

The only consistent way I can recreate it is:

1. Open Meta Quest Browser on the quest device. (doesn't occur with emulator)
2. Don't pickup / use controllers only use hand tracking
3. Use hand tracking to Enter VR
4. Use the meta quest menu hand gesture (looking at right palm and pinching)
5. Press the "Quit" button that the meta quest browser automatically adds to the top of the page

This causes the memory access error to occur in an unsafe input system method. I am unfamiliar with the input system's API, but I tracked down where the error occurs and added this temporary workaround.

Like I said since it doesn't occur with your samples so I think it may be an issue with the newer version of the hands / input packages or my own project's setup.

[De-Panther]

Good catch. Might be the newer versions.
I'll push a fix soon.