You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 16, 2022. It is now read-only.
The issue raised from chrome origin security specification which now require a signed certificate in order to serve onto SSL, which is required in order to access device media(e.g camera)
It was fixed by spawning an certificated http-server for instead of the webpack-dev-server .
VR Mode Compatibility
I then encountered an issue where aframe failed to enter VR mode due to compatibility issues of the newly drafted onvrdisplaypresentchange Event which was patched yesterday at aframe#2920. This was fixed by downloading the master build in order to apply the patch.
Orientation Lock
I am currently facing an issue with the orientation lock, PR and updates are soon to follow
Action Items
Enable hot reload of the dev server using the watch functionality
Once aframe releases v6.2, move back to package management installation
I still recieve the error screen.orientation.lock() failed due to A call to screen.orientation.lock() or screen.orientation.unlock() canceled this call. which is related to the Screen Orientation Lock API which is used at AFrame
Will investigate and follow-up 🙏
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Firefox is returning the error "Can't access user media :()" when access
http://localhost:8080/
afteryarn run start-server
.The text was updated successfully, but these errors were encountered: