I have recently updated my desktop chrome and mobile android chrome.
Since that I have trouble getting my location. It doesn't work with my website JS geolocation script nor here:
http://html5demos.com/geo
It just says failed. I have tried removing location access privilege and changing to ask but it doesn't work.. Any idea what is the reason for that.
You will need to have WAMP accept requests on port 443 and create a certificate in order for the browsers to not complain. There are detailed instructions here: http://www.lmhproductions.com/31/how-to-setup-ssl-on-wamp/
Related
I've searched and searched but I guess I can't find the answer I'm looking for.
I'm working on a web app with Google maps and I am having a lot of difficulties trying to debug and test it. I finally found out why I keep getting errors due to chrome blocking calls made not via HTTPS. The app works in Firefox, but not in chrome or any other browser I've tried, safari, dolphin, etc. (All works great locally of course)
What should I do? Is my only option to pay for SSL cert for my free hosting account that I'm using to test my app? I'm just a mid-level developer who isn't really ready to pay for hosting just yet... Am I missing something super common that most developers take advantage of in terms of having some solid way of testing? Hopefully, that makes sense!
try using https://ngrok.com/ it might work out.
It tunnels your local url to public with https too.
For Chrome, there is a flag for this at chrome://flags/#allow-insecure-localhost.
Click on Enable and restart Chrome. From now on invalid certificates on localhost (and just on https over localhost) are accepted.
When attemping to use HTML5 Geolocation method, I consistently get TIMEOUT errors when using Chrome. I know similar questions have been asked, but all answers I've read direct the developer to use HTTPS & not a local env (ie: file:///).
I'm testing with the exact code sample from the Example block at Mozilla Geolocation.getCurrentPosition().
I'm using Chrome Version 54.0.2840.98 (64-bit).
I am using SSL / HTTPS (not self-signed, cert has valid cert auth).
I have confirmed the Location Service is allowed for the domain in question in Chrome Preferences.
I have successfully tested the same code using Safari.
I have tried with & without a valid Google API key with no difference.
I have enabled Google API Billing for the specific project that this API key is tied to in Google Dev Console.
Here's a screen shot of the error in console.
I don't know where else to look or what to try. Any help is greatly appreciated.
When I try to login into my website using firebase-authentication with a Nokia Lumia 520 Phone 'auth/web-storage-unsupported' error code is thrown. I'm using AngularFire 2.0.1. Is there any way I can work around this issue becuase some of my users still use these phones with older version of Internet Explorer.
From Firebase Documentation
Thrown if the browser does not support web storage or if the user disables them.
Probably your device has disabled cookies for your website, or does not support them at all.
Third-party cookies may be disabled in your browser. Enable them and try again. It worked for me.
for me the problem was that firebase only work in https and localhost domain. so when I run it locally in my computer it work well. but when I test it in my phone via an IP it suddenly throw this error. so you should find a way to run it with localhost domain. or try to just test with https enabled
I am using a WebRTC demo application for screen sharing. The demo works perfectly fine but when I try to run the same code in localhost or my own remote server, the code doesn't run.
Any ideas on how can I fix this issue?
Screensharing in Chrome only works over an SSL connection(). You can use a self-signed cert and simply accept it in your browser(this is for Chrome < M36).
Also, for Chrome >M36 you must now use the Chrome.desktopcapture API and the usual way of modifying media constraints and enabling screen-sharing in Chrome internals will not work in newer versions of chrome.
The API is farely simple and MUCH more robust than the previous given option in the media constraints.
I'm facing an issue with chrome 28.
I build an application that use the webcam to take picture.
I had no problem with it, but since I upgrade to chrome 28, my application is not working anymore (I'm getting an error with the getUserMedia function).
Here is the message : {"constraintName":"","message":"","name":"PERMISSION_DENIED"}.
If I try to run the app code on a simple html and httpserver, I got no problem with it.
And when using the APP I'm not asked anymore if I allow the usage of the webcam.
I've tried to turn on some chrome flags for webrtc but nothing change.
Does anybody has/had this issue ?
Thanks !
You may have accidentally denied access to the webcam in the past. If your site is being served via HTTPS, that setting will be saved. This page has a description of that error and a screenshot that shows what the settings should look like.
Once you have tried all the above:
Make sure that there is no other program or browser tab accessing the camera.
If you are on Android, open a camera App to make sure that the it's not stuck (it happens to me all the time with Cyanogen).
What the browser is reporting is that a media source is missing (might be permissions, config or harware). More info here: http://webrtchacks.com/getusermedia/
Once you have made sure that the site is not blocked in Privacy content settings, Goto chrome://flags/#enable-permissions-bubbles in Chrome and ENable these . Now the notification will appear asking for permission to access the web cam , just click allow .