Skip to content
This repository has been archived by the owner on Jun 16, 2022. It is now read-only.

"Can't access user media :()" #4

Open
abraverm opened this issue Jul 31, 2017 · 2 comments
Open

"Can't access user media :()" #4

abraverm opened this issue Jul 31, 2017 · 2 comments

Comments

@abraverm
Copy link
Contributor

Firefox is returning the error "Can't access user media :()" when access http://localhost:8080/ after yarn run start-server.

@shakedlokits
Copy link
Contributor

shakedlokits commented Aug 2, 2017

Checkpoints

Media Access

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

@shakedlokits
Copy link
Contributor

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants