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

Sensor access disabled by default in Safari from iOS 12.2+ #3976

Open
richtr opened this Issue Jan 29, 2019 · 6 comments

Comments

Projects
None yet
6 participants
@richtr
Copy link

richtr commented Jan 29, 2019

AFrame VR will no longer work on iOS according to the release of iOS 12.2b without changing the default Safari settings on devices:

w3c/deviceorientation#57 (comment)

Both deviceorientation and devicemotion sensors will be disabled by default in Safari from iOS 12.2+. Users will need to enable Settings > Safari > Motion and Orientation access to continue to use AFrame.

AFrame relies on polyfilling WebVR from these sensors on iOS via its dependency on webvr-polyfill (which in turn relies on cardboard-vr-display).

Blog post discussing change @ https://medium.com/@firt/pwas-on-ios-12-2-beta-the-good-the-bad-and-the-not-sure-yet-if-good-a37b6fa6afbf

Is there any plan to work around this change in AFrame?

@dmarcos

This comment has been minimized.

Copy link
Collaborator

dmarcos commented Jan 29, 2019

Those are bad news. Without access to sensors not sure if there’s anything we can do.

@jsantell

This comment has been minimized.

Copy link
Contributor

jsantell commented Jan 29, 2019

Looks like Generic Sensors is also not supported either. To be fair, deviceorientation and devicemotion are terribly abused APIs, but not sure of a work around currently for iOS.

@griffin2000

This comment has been minimized.

Copy link

griffin2000 commented Jan 29, 2019

There is a W3C thread on this here (specifically about adding a permission pop up) be sure to comment how important it is that this gets fixed! w3c/deviceorientation#57

@geoffreygaren

This comment has been minimized.

Copy link

geoffreygaren commented Jan 29, 2019

Does AFrame VR offer a fallback interaction model for desktop users and mobile users who choose not to allow sensor access?

@dmarcos

This comment has been minimized.

Copy link
Collaborator

dmarcos commented Jan 29, 2019

@geoffraygaren Yes, on desktop you can use mouse / keyboard to move the camera and touch on mobile.

@ngokevin ngokevin added the mobile label Jan 31, 2019

@dmarcos

This comment has been minimized.

Copy link
Collaborator

dmarcos commented Feb 5, 2019

Current conversation about spec:
w3c/deviceorientation#57

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment