Custom fallback URL

[ukito-pl]

Hi,
are there any plans to add option to define custom fallback URL that user will be redirected to if SceneViewer on Android fails to open?
I can see here:

model-viewer/packages/model-viewer/src/features/ar.ts

Line 303 in 6a70645

encodeURIComponent(locationUrl.toString())};end;`;

that it is currently hard coded to current location url with added hash.
It may become troublesome behavior when using modelviewer via iframe on diffrent domain, beacuse then there is no way to inform user that something went wrong (fallback url is being blocked by browser because domains don't match).

Also it would allow to set fallback url to redirect user to Google Play Store to download or update Google AR Services. It is probably the most common use case for fallback url from what I saw on other solutions.

[elalish]

This is an interesting idea; can you put together a Glitch or other repro link where I can repro the problem you're describing?

[davidc-epigraph]

Is there any workaround to implement a fallback URL? curious as having a customer where we have no access to source code (CMS is Magento) but it appears as they something in place that's actively blocking model-viewer from fetching

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'toString')
    at s.[openSceneViewer] (our-component.min.js:1250:96)
    at s.activateAR (our-component.min.js:1236:18609)
    at XC.[onArButtonClick] (our-component.min.js:1600:5821)
    at Vb.handleEvent (our-component.min.js:1276:7509)
    at HTMLSlotElement.t (field-lounge-chair.html:20:5854)
    at HTMLSlotElement.nrWrapper (field-lounge-chair.html:20:30045)
[openSceneViewer] @ our-component.min.js:1250
activateAR @ our-component.min.js:1236
[onArButtonClick] @ our-component.min.js:1600
handleEvent @ our-component.min.js:1276
t @ product.html:20
nrWrapper @ product.html:20

[elalish]

Things like this are why we prefer WebXR, which stays in the browser and avoids all this and many other problems. Is there a reason you don't prefer that?

[tanaydimri]

Hey @elalish,
Our main reason to not use webXR was the lack of support on iOS with Safari and effectively all other browsers (on iOS). I went to check again on MDN Docs to verify if we missed some updates on this front but looks like iOS is still lacking support for the same.

I think I should even add that we are only displaying the AR button in this case and not using the viewer. After looking at the source a bit, it looked like the model viewer component wasn't able to fetch the parent page's location for some reason.

Thank you and we would appreciate any help with this issue.

[elalish]

Fair, but I'm not sure why that matters here. Scene Viewer is equally unsupported on iOS; your only AR option on iOS is Quick Look. On Android your only options are Scene Viewer and WebXR; based on your problem, I'd recommend switching to WebXR. All three of these modes have unique functionality, so there's not really such thing as being more or less consistent. We can only deliver actual consistency when iOS ships WebXR, so please let Apple know you'd like that.

[tanaydimri]

Wouldn't we all like it if Apple for once did something in collaboration with the community, sigh!!

Thank you so much for your inputs though, using ar-modes="webxr quick-look" might just do the trick if I understood your correctly. We are trying to have a clone of the client site ready for testing today, but at least setting these ar-modes from the dev console got rid of the error. Nothing launched but that might just be because of the device I was running it on (will try on a mobile phone once our test environment is ready)

Once again, thank you. Really appreciate your quick responses :)