navigator.geolocation.getCurrentPosition doesn't work on android google chrome
Solution 1
You can try this. It seems to work on my device (Samsung Galaxy Nexus running Chrome 27.0.1453.90 on Wi-Fi (no data connection, no GPS on))
navigator.geolocation.getCurrentPosition( function(position) { alert("Lat: " + position.coords.latitude + "\nLon: " + position.coords.longitude); }, function(error){ alert(error.message); }, { enableHighAccuracy: true ,timeout : 5000 } );
The problem is that alert only takes strings (in it's original form) however you are passing 2 doubles. Modify the alert box for example to alert('Hey', 'Hello');
and the output will be only Hey
. Change the ,
to +
and you'll get the concatenated strings HeyHello
. You can't use a +
sign inside the alert
as the equation will be first executed and then displayed.
Hope this makes it clear.
Solution 2
THERE IS A WORKAROUND: to watchPosition call, and wrapping this in a 5 second wait before clearing the watchID. Code below;
var options = { enableHighAccuracy: true, maximumAge: 100, timeout: 60000 };
if( navigator.geolocation) {
var watchID = navigator.geolocation.watchPosition( gotPos, gotErr, options );
var timeout = setTimeout( function() { navigator.geolocation.clearWatch( watchID ); }, 5000 );
} else {
gotErr();
}
I haven't played around with the "options" values or the timeout delay at the moment, but the above code brings back accurate positioning info on every platform I've tried.
Solution 3
Just finished testing a bunch of mobile devices and the Javascript Geolocation. I used the example code from Google in order to make sure that the problem is not in my own code.
Chrome for Android 4.4 does not seem to work with GPS-only location services and neither does the 2.3 stock browser. They both need "High accuracy" - the use of wireless and 3G/4G networks.
The funny thing is that Firefox for Android works without any problems GPS-only. Only the stock Android browsers (Chrome + Mobile Safari) fail with GPS-only location settings.
And the rest of the gang - Lumia WP8 with GPS, Windows and Linux (both with ADSL) worked perfectly with any location settings.
Solution 4
Well, I ran into this problem yesterday and the issue was that the Geolocation API can only be used over HTTPS. It will work on http://localhost
but for other devices, you need to be on a secure connection.
Hope it helps!
Solution 5
After many hours of seeking solution for error3, i only can reboot my phone, and geolocation starts work as usually. So bad...
Comments
-
Andrey Koltsov over 3 years
This code:
navigator.geolocation.getCurrentPosition( function(position) { alert(position.coords.latitude, position.coords.longitude); }, function(error){ alert(error.message); }, { enableHighAccuracy: true ,timeout : 5000 } );
https://jsfiddle.net/FcRpM/ works in Google Chrome at my laptop, but on mobile HTC one S (android 4.1, GPS off, location via mobile networks and wifi enabled), connected to internet via WiFi.
- Default browser works fine.
- Google Chrome, Opera, Yandex.browser for android fails with "Timeout expired".
other android apps locates me correct.
-
Andrey Koltsov almost 11 yearsproblem not in alert('Hey', 'Hello'); that I see one line, problem in that code doesn't return location. Your code shows "Timeout expired" alert HTC One S Chrome Chrome 27.0.1453.90
-
Adrian almost 11 yearsThis might sound crazy, but are the location services turned on on your device? I've just tried the same code again without having the Google Location Access turned on and I got the error you mentioned. Within Chrome, go to Settings -> Content Settings -> Google location settings and see what your browser settings are
-
Andrey Koltsov almost 11 yearsYes, location services turned on, code works in default browser, but doesn't work in Chrome
-
Adrian almost 11 yearsUnless you've set your Chrome to not use your location, I can't seem to find any other good explanation why the above code might not work. I've tested on my device on Chrome and the native browser and works perfectly. Sorry if I can't help more.
-
sharpper almost 11 yearsSeems that enable high accuracy fixed this for me. Noticed it was not hitting the GPS at all without this option set to true.
-
Andrey Koltsov over 9 yearsIt isn't a native application, it is Javascript
-
Guy Korland over 9 yearsare you sure the workaround works? I just tried it and it didn't
-
delkant over 9 yearsyes, it should work, check that your browser allows location requests from the host where your scripts are being loaded. It happened to me before that my domain was in the black list of the browser so location wasn't shared to the site.
-
Imran Omar Bukhsh over 8 yearsI used code from Adrian ( Javascript ) to check what the issue was and it says "Application does not have sufficient geolocation permissions". So the answer could be right.
-
Tony Garnock-Jones over 7 yearsI have filed a bug against chromium: bugs.chromium.org/p/chromium/issues/detail?id=620003 . No response yet.