-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Android Webview issue #3243
Comments
Issue is specific to Android System WebView 62.x or a WebView using Chrome 62.x. It's resolved in Chrome 63, 11 days away from release. We've bundled the CrossWalk WebView with our app and are conditionally using it when we detect the user has 62.x installed. |
Chrome 63 should have shipped. @meatwallace @kyriakosproto Can you confirm if this issue is gone? |
@dmarcos - definitely resolved in Chrome 63. |
Cool, thanks! |
Сайт должен начинаться с https, тогда будет работать. |
Hello,
We experience an issue when we preview aframe scenes through Webview in Android apps after Chrome/Webview update to version 62.0 (was working fine on previous versions). The aframe scene initializes and works fine but it does not respond to the device movements (seems like it doesn't communicate with gyroscope to update vr camera's rotation), although rotation using touch events works fine.
We have this problem embedding our project, that uses aframe version 0.5, also had the same result when we tried to embed examples from aframe's website (including https://aframe.io/examples/showcase/helloworld/ which uses version 0.7)
The following permissions/features are defined in AndroidManifest.xml
Here is a snippet of the webview initialization code from the Activity class file
Following are the contents of the build.gradle file
we tested this on 2 Android devices:
Does anyone else have this issue? or knows if there is a fix for that?
The text was updated successfully, but these errors were encountered: