issues with webxr on meta quest

Hello!

After recently upgrading an older tour to version 1.22, webvr or rather webxr doesn't seem to be working on the Meta Quest headset.

This tour uses a bit of a custom engine (based on krpano of course), so I can't exactly share the whole codebase, but the point is:

• webvr, gyro2 and krpano itself are both 1.22, same build
• webvr plugin's onavailable event fires and the iswebvr and iswebxr attributes are all true
• there is a button that we click to call the entervr() function so user interaction is there
• and when that happens, instead of entering vr, there's a black screen for a few moments with the loading indicator, and then the page reloads
• the official krpano examples work just fine

• no errors in the console whatsoever
  
  What is the bare minimum code for the webvr plugin to function? Just adding the plugin, setting keep to true and then calling the plugin's entervr() function should work right?
  
  I'm gonna continue to try and figure this out but if anyone got any tips, I'd appreciate that. Thanks.

  
  

// Ensure WebXR is supported
if (navigator.xr && navigator.xr.isSessionSupported) {
    // Check if immersive VR is supported
    navigator.xr.isSessionSupported('immersive-vr').then((supported) => {
        if (supported) {
            // Wait for a user interaction (e.g., button click) to start the session
            document.getElementById('enterVrButton').addEventListener('click', () => {
                navigator.xr.requestSession('immersive-vr').then((session) => {
                    console.log('WebXR immersive session started!');
                    // Now you can initialize your XR experience with the session
                    // For example, set up a WebXR controller or renderer
                }).catch((error) => {
                    console.error('Failed to start WebXR session:', error);
                });
            });
        } else {
            console.log('Immersive VR is not supported.');
        }
    });
} else {
    console.log('WebXR is not supported.');
}

Also, running this code it gets to the "WebXR immersive session started" part - I assume the WebVR plugin does something similar internally, so something the initial stuff is causing the page reload :(

I have managed to narrow down a section of the code that is still quite long but much less than the entire engine we're using. Once I've found the particular part that is conflicting, I'll post it here so that if anyone runs into something like this they may know what the cause is.