Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Next stable Chrome (79) implementing WebXR Device API, will break aframe
See original GitHub issueDescription:
- A-Frame Version: 0.9.2
- Platform / Device: Chrome 79 (you can try on Beta, will be out first days of December 2019)
- Reproducible Code Snippet or URL:
Just open an aframe application with Chrome 79 beta. Otherwise, look here:
-
open this link, it’s an app using latest aframe : https://nicolo-carpignoli.herokuapp.com/examples/places-name/
-
open console
-
you can see the error. it’s from device.js file, error is in accessing
navigator.xr.requestDevicethat is not present. APIs are changed lately. Code needs to be changed simply with a sanity check.
This potentially breaks every aframe app.
Thanks for the attention
Issue Analytics
- State:
- Created 4 years ago
- Comments:13 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@rajsite Updating to 1.0.3 will solve the issue.
I filed https://github.com/aframevr/aframe/issues/4322 about controller handling