1

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. Error Msg in Chrome Console

I don't know where else to look or what to try. Any help is greatly appreciated.

user2977468
  • 183
  • 1
  • 13
  • Are you answering "Yes" to the prompt from the browser asking you if you will share your location? Do you have a popup blocker installed? Have you just tried pasting that example code into the `console` and running it from there. That worked without issue for me. – Scott Marcus Dec 14 '16 at 00:40
  • Yes to ^ and you also need to post your relevant code. – Phillip Chan Dec 14 '16 at 00:44
  • @ScottMarcus - I have said yes, previously, to the question regarding sharing my location & I'm seeing the GPS location indicator on the right hand side of my address bar. Unfortunately, I am still seeing the error if I paste example directly into console. I'm going to reset browser to default / factory settings & re-test. – user2977468 Dec 14 '16 at 00:48
  • @PhillipChan - Relevant code is in **Example** listed above. – user2977468 Dec 14 '16 at 00:49
  • 400 Error means this: http://stackoverflow.com/questions/19671317/400-bad-request-http-error-code-meaning There must be some encoding going on in your Chrome. – Scott Marcus Dec 14 '16 at 00:52
  • @ScottMarcus - I've reset to Chrome original defaults & error persists. I'm going to read your suggested article now. Ty. – user2977468 Dec 14 '16 at 00:53
  • @ScottMarcus - If I reset Chrome to defaults (again), navigate to a generic page (IE: Google.com), and paste the example code directly into the console - I am greeted with the pop-up "Google would like to share your location...". I click yes, then the same error pops up in the console as previous. This test completely abstracts my source code from the issue. :/ – user2977468 Dec 14 '16 at 00:59
  • Are you behind a firewall or any kind of appliance that could be modifying the request? – Scott Marcus Dec 14 '16 at 01:02
  • @ScottMarcus - No, I'm not. Currently working from home w/ a pretty standard env. But I did figure something out. I'm working in OSX 10.11.6. I created a new user in my O.S. Logged in as that user. Opened Chrome & pasted example code into console, returning a successful result. Changing the local user account resulted in the difference. – user2977468 Dec 14 '16 at 01:05
  • Hmmm. Well, you're past my pay grade on that one! – Scott Marcus Dec 14 '16 at 01:10
  • @ScottMarcus - That makes two of us! I'm just going to re-create my local user account. Not sure of the root cause here, but thank you very much for helping me narrow it down. – user2977468 Dec 14 '16 at 01:12

0 Answers0