-
Notifications
You must be signed in to change notification settings - Fork 807
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AR on Android Chrome 88 fails #2007
Comments
What you're saying here is different than the comment you left on the other bug: #1694 (comment) Is this a crash in AR or on model load? The way you describe it here, it does indeed sound like a dupe of #1694. |
Actually this looks like a separate Chrome regression. It's fixed in 89, but I'm very sorry this slipped through into 88! Can you verify that it's working in Chrome beta? |
Yes, it's different (than what I wrote in 1694). Here really the only thing I do is open the AR examples in Chrome and try to start AR, but it doesn't. Now on one of the phones, it works, in both Chrome 88 and 89. But on the other one, it does not start AR, not even in Chrome 89! The one working is a Huawei P20, while the non-working is a Huawei P30 Lite. Both have the exact same Chrome versions, and run Android 10, and are totally regular.. I'm sorry that I don't have a clue myself where the difference is. If there is anything I can provide to help find the issue, let me know. Thanks! |
@klausw Perhaps another Chrome issue, as it repros in 89? |
@danbaechtold , can you please check your specific release number from chrome://version ? There was a known bug affecting some devices where AR doesn't start correctly, https://crbug.com/1169822 . That should be fixed for Chrome Beta >= 89.0.4389.31, and Chrome Dev/Canary >= 90.0.4404.0. |
The Beta used is a newer one (89.0.4389.48), but the bug is still there. It also doesn't work
in Chrome Dev (90.0.4413.0)..
I press "View in your Space" on the Chair example, but then only the button
disappears, and nothing else happens..
|
@danbaechtold - could you please look up the Android OS version for both the working Huawei P20 and for the non-working Huawei P30 Lite? It's shown in chrome://version, for example "OS: Android 11 Build/RQ2A" on my phone. Also, would you mind trying a couple of other AR sites to rule out other potential problems? https://modelviewer-ar-test.glitch.me/ - this is a test page using Scene Viewer, not WebXR https://immersive-web.github.io/webxr-samples/immersive-ar-session.html - a simple WebXR AR example https://immersive-web.github.io/webxr-samples/ar-barebones.html - another test, with DOM Overlay Thank you for your patience! We don't currently have a known issue that would cause this, so it may be hardware or driver specific. |
One more thing to try would be to disable "Android SurfaceControl" in chrome://flags for Chrome Beta. Direct link: chrome://flags#enable-surface-control |
@klausw Thank you for looking into it! Here are my findings (still not working):
*) Pressing the AR button a second time started a fullscreen session (but just showing the model-viewer, not in AR) Further observations:
|
@danbaechtold , thank you for the very thorough test. I'm afraid the issue is simply that these phones aren't supported by ARCore. The list at https://developers.google.com/ar/discover/supported-devices#google_play includes the Honor 8X and Huawei P20, but not the Nokia 5.3 or Huawei P30 Lite. I was under the mistaken impression that this was a regression, but I assume these had never worked with model-viewer? For background, the "Enter AR" button or equivalent appears when @elalish , I think it would be worth following up to have better error reporting for cases like these where the session fails to start. It appears as if |
Oh, no.. sorry I didn't realize that this could be the reason, as both phones where purchased only a few months ago. So, I hope I didn't cause you too much trouble, and if it is some how possible to improve the check or error, then we can give such users a better explanation. Thank you so much, |
No worries, it was my mistake to assume that it's a regression even though you didn't claim that in your report. I had recently been investigating related issues and was worried that my recent fix was not effective on some devices. Also, the current error handling is admittedly not very user friendly. To some extent this is by design, since for privacy reasons the application isn't supposed to be able to tell if a session failed due to missing hardware support or due to the user declining a consent prompt, but I think it should be possible to be a bit more helpful here. |
Small update, regarding the Noka. I rechecked and there too it shows the "Failed to start immersive AR" error, as it should. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Description
When I try your AR examples page (https://modelviewer.dev/examples/augmentedreality/), 4 of 5 of my Android-Chrome88 devices fail to enter AR mode. Pressing the "View in your space" btn will just make the button to disappear. Trying the 3rd demo (2nd austronaut), it says "AR not supported on this device".
The devices I have are mid-range and btw 1-2 years old, all up to date, with normal end-user settings.
My first guess was that it might be related to this Three.js bug: mrdoob/three.js#21126
But the latest model-viewer seems to have the fixed version already..
Let me know if I can help or if you need more info.
Thanks!
Browser Affected
OS
The text was updated successfully, but these errors were encountered: