This might be due to WebVR vs WebXR and a difference between Hubs vs Hubs Cloud. If I remember correctly there was a bit of a rush when WebXR only became available on the Quest browser. Maybe some added compatibility was added, either in FFxR directly or in Hubs but not Hubs Cloud or vice versa.
Configuration
Wolvic version: 0.9 Wolvic build ID: d8f85016 (AC 63.0.0)
Hardware: Quest 1
Steps to Reproduce
Current Behavior
Impossible to enter immersive mode
Expected Behavior
Enter immersive mode, like on hubs.mozilla.com
Possible Solution
This might be due to WebVR vs WebXR and a difference between Hubs vs Hubs Cloud. If I remember correctly there was a bit of a rush when WebXR only became available on the Quest browser. Maybe some added compatibility was added, either in FFxR directly or in Hubs but not Hubs Cloud or vice versa.
Context
Error Logs and Stack Traces