-
Notifications
You must be signed in to change notification settings - Fork 23
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
street view realities #14
Comments
Not sure if you resolved this: nothing that needs the geolocation api's will work unless you are using HTTPS connections (limitation of mobile web views) |
Nope it didn't work. Not on mobile, was on web.
On Mon, May 1, 2017 9:02 AM, Blair MacIntyre [email protected] wrote:
Not sure if you resolved this: nothing that needs the geolocation api's will
work unless you are using HTTPS connections (limitation of mobile web views)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Erin [email protected]
|
Sorry, I should have been more general: not mobile, "modern" web views. Most browsers won't let you use the geolocation api's if you aren't using https |
Ya no I tried that, we discussed this last time for viewing the website before
when I had issues, I don't think that it, nothing loaded after I npm install'ed
everything remember?
On Mon, May 1, 2017 3:52 PM, Blair MacIntyre [email protected] wrote:
Sorry, I should have been more general: not mobile, "modern" web views. Most
browsers won't let you use the geolocation api's if you aren't using https
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Erin [email protected]
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
These examples did not build after in npm installed everything, there were at least two others that showed up with blank pages where as others did. Did I need to modify any code anywhere to get it to run?
The text was updated successfully, but these errors were encountered: