Scene Viewer crashes on some Samsung Galaxy devices

[cdata]

Please refer to discussions in #693 (comment) for related context. The gist of the issue is that as of the hotfix release v0.5.1, Scene Viewer appears to be crashing when launched from Chrome by <model-viewer> on some Samsung Galaxy devices, including the A5, S7 and S7 Edge.

[sydadder]

Do we have an eta on this fix? It is not device specific but Android version <=8 issue

[cdata]

@sydadder I cannot give you an ETA, only an assurance that the team is aware of the bug and is looking into it. That's the best I can do for now, but I'll update this thread as there is more to share.

[TRSasasusu]

Also, Xperia XZ1 SOV36 crashed after updating ARCore SDK to v1.11.0. Scene Viewer works on this device previously (but I don't know the previous ARCore SDK version...).

• Android version: 8.0.0
• Chrome version: 76.0.3809.111
• Crashed package name: com.google.ar.core
• URL where crashed: https://googlewebcomponents.github.io/model-viewer/examples/augmented-reality.html

[cdata]

I can't give y'all an ETA, but I can confirm that the source of this crash was identified and a fix was landed for it. I'll update here when I learn more.

[letsrock85]

Hello,

I was looking for a way to switch to ARView mode automatically and came up with placing this.activateAR() function into onModelLoaded event. But in the end I have the same issue, problem with the Anchor.Click - Intent stuff.

I'm currently on the latest 0.5.1 version with the hot fix implemented mentioned above, but it doesn't really solve that problem.

Any suggestions how to run AR View mode skipping the process of clicking onARButtonHandler thing?

Thank you

[cdata]

@letsrock85 The browser requires user interaction to trigger an intent on purpose. It's a protection for users. For example, it keeps a malicious site from spamming users with unexpected intents.

This article by Paul Kinlan describes how you can use a 302 redirect to trigger an intent. Depending on your use case, this might achieve the effect you are going for.

[sydadder]

@cdata You mentioned 'fix was landed for it'. What would be the next step for us as users? I'm guessing that the changes haven't been rolled out yet and we need to wait for a confirmation once done isn't it?

[cdata]

The next step is to wait patiently until an update rolls out publicly. I'll do my best to keep this thread updated when that happens.

Please keep in mind that Scene Viewer is a different project from <model-viewer>. Scene Viewer is not open source, and is managed according to its own set of goals and timelines. The best I can do here is facilitate communication back and forth as I receive new information.

[hybridherbst]

Any news on this? It's been a month now, and the latest ARCore update was on Aug 28 without the fix.

The affected Samsung phones have a giant market share in Europe, some customers of us are getting pretty annoyed by now... This doesn't really help with getting people to support and invest in AR projects on the web :(

[cdata]

@soraryu acknowledged, and I'm sorry for the delay. Scene Viewer is a different team. They have their own processes and their own reasons for shipping (or not), and I'm not at liberty to disclose everything that I know about that.

What I can say is that while the bug was fixed very quickly, the public update was unexpectedly delayed multiple times for unrelated reasons. Unfortunately there is not much that the <model-viewer> project can do to make a difference here.

I'm sorry on behalf of the Scene Viewer team for the inconvenience, and I will update this thread when I have confirmed that the fix has been made public.

[cdata]

Thanks for your continued patience everyone. I can't offer specific details yet, but please stay tuned for an update on this issue very soon!