-
-
Notifications
You must be signed in to change notification settings - Fork 35.2k
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
webXR AR broken on Android Chrome 88 #21126
Comments
Can you please try it with the current https://raw.githack.com/mrdoob/three.js/dev/examples/index.html Same result? |
Tried it myself on a Pixel 4a. The |
Yes... It's unfortunate, but seems like Chrome 88 broke all the projects done pre-r125 🙁 |
They must have made a slight tweak to how promises are resolved. |
Well, at least #20754 is not a big PR. If a project can't afford the budget to upgrade to the latest |
Older versions of three.js (until r125) have the following issue mrdoob/three.js#21126 present which breaks certain WebXR experiences like "moonrider" and "construct chess". This workaround makes sure that any WebGL context is marked as XR compatible when possible which means that applications no longer have to mark it manually and in the correct order. This fix is verified to work on both "moonrider" and "construct chess" and also doesn't break sample WebGL pages that don't use WebXR.
Describe the bug
My test device runnning Android 8.0.0 updated to Android Chrome 88 today, and the three XR AR samples no longer work.
https://threejs.org/examples/?q=webXR#webxr_ar_cones
https://threejs.org/examples/?q=webXR#webxr_ar_hittest
https://threejs.org/examples/?q=webXR#webxr_ar_paint
I am describing the issue on the webxr_ar_hittest example.
To Reproduce
Steps to reproduce the behavior:
-Update Android Chrome to v88.
-Go to https://threejs.org/examples/?q=webXR#webxr_ar_hittest
-Click on "Start AR".
-This is not working and there is an error in the console.
Expected behavior
We should go in AR (it was working before with Chrome <88).
Screenshots
Platform:
The text was updated successfully, but these errors were encountered: