Hubs stuck on loading screen in Chrome on Android and Windows if webvr/xr flags are enabled

[brianpeiris]

If webxr and/or webvr flags are enabled in chrome://flags, hubs will fail to load.

[brianpeiris]

There's some odd interaction with webvrpolyfill going on here. aframe.io does not seem to suffer from this problem, so it seems specific to Hubs.

[johnshaughnessy]

Burned me for a few hours today. Will be nice to figure this out

[johnshaughnessy]

I'm not sure if those are the only flags that cause this issue. I have disabled those flags and still cannot get in on chrome.

edit: nevermind. disabling the webxr flag seems to have fixed my issue.

[johnshaughnessy]

I can get past my issue by not loading our service worker:

hub.js:

  subscriptions.setRegistrationFailed();
  //if (navigator.serviceWorker) {
  //  try {
  //    navigator.serviceWorker
  //      .register("/hub.service.js")
  //      .then(() => {
  //        navigator.serviceWorker.ready
  //          .then(registration => subscriptions.setRegistration(registration))
  //          .catch(() => subscriptions.setRegistrationFailed());
  //      })
  //      .catch(() => subscriptions.setRegistrationFailed());
  //  } catch (e) {
  //    subscriptions.setRegistrationFailed();
  //  }
  //}

[johnshaughnessy]

Sorry for the spam -- I withdraw the above comment. It seems to me that it's only the WebXR flags that cause this issue for me, not the WebVR flag.

[arpu]

aframevr/aframe#4002

[brianpeiris]

It seems the Brave browser is also affected by this. Probably the new Edge as well.

[brianpeiris]

Fixed in #1231