Model-viewer: SceneViewer doesn't work on chrome with android

Created on 16 Jun 2020  路  4Comments  路  Source: google/model-viewer

AR doesn't work on chrome neither with android, just me?

if I insert the code on wordpress I have this problem, even on the html page, while on Wix it works, how come?

bug

Most helpful comment

Okay, it looks like the problem was relative URLs failing to launch SceneViewer, which I'm in the process of fixing. I believe this will also fix the Samsung Browser issue, since it is based on Chrome 75 which does not include webXR. Therefore I think the webXR demo was failing for the same reason: it was actually trying to launch SceneViewer.

All 4 comments

Good question; can you post links here where it does and doesn't work? I'd be happy to take a look. Also, does the javascript console show any interesting errors or warnings? A possible issue is not having the proper CORS headers on the glTF.

Hello, I wanted to share my experience and I think we have the same symptom.

I have tested the following two links with model-viewer using WebXR and SceneViwer, I have also downloaded the same demos from GITHUB and uploading them to my server the same thing happens (The launch AR button dont start the AR).

Links:

(WEBXR) https://modelviewer.dev/examples/webxr.html
(WEBXR + SCENEVIEWER) https://modelviewer.dev/examples/augmented-reality.html

Using model-viewer:

version 1.0

Browsers version and device:

Samsung browser (11.2.2.3 GalaxyS7 and 11.2.2.3 GalaxyS10) in both case happen the same:
WebXR - AR button dont start the AR.
Sceneview - AR button dont start the AR.

Google Chrome browser (83.0.4 GalaxyS7 and 83.0.41 GalaxyS10) in both case happen the same:
WebXR - This is the ONLY case where the button start the AR.
Sceneview - AR button dont start the AR.

This start since model-viewer version 1.0, it was working in 0.10

@FrankHiguera Thank you for the details! We've managed to repro all of this on an S8+.

As a side note, modelviewer.dev serves the latest master, which is now ahead of 1.0.

Okay, it looks like the problem was relative URLs failing to launch SceneViewer, which I'm in the process of fixing. I believe this will also fix the Samsung Browser issue, since it is based on Chrome 75 which does not include webXR. Therefore I think the webXR demo was failing for the same reason: it was actually trying to launch SceneViewer.

Was this page helpful?
0 / 5 - 0 ratings