Network location provider at 'https://www.googleapis.com/' : Returned error code 403 in Webapp

Question

I am using Geolocation.watchPosition() and I get the following error on callback

Network location provider at 'https://www.googleapis.com/' : Returned error code 403.

This seems to be only happening in chrome desktop browser. firefox seems to be fine. This is also just started happening today, I have never come across this error before within my web app using the Geolocation.watchPosition().

Update: bug https://bugs.chromium.org/p/chromium/issues/detail?id=753242

Solution 1

This happened to me too. I had to enable location services on my Mac.

Solution 2

After looking for an answer, I think there is something wrong with Google

I tried it with developers.google site

Safari: worked
Google Chrome: failed

Solution 3

Just restart Chrome (Force Quit), and it will work fine!

Solution 4

It is indeed a chrome issue, to get around it you have to check your developer dashboard and make sure that your API key has no warnings.

Also, you need to make sure that the proper usage restrictions are in place for the development phase:

This key is unrestricted. To prevent unauthorized use and quota theft, restrict your key. Key restriction lets you specify which web sites, IP addresses, or apps can use this key.

More information can be found here.

Solution 5

Currently there is might be an issue with google map API. I was also using google map API yesterday and it was not working as it should be. And then i started using this free plugin and it worked for me like a charm. http://www.geoplugin.com/

View more solutions

Comments

[Harry]

did you find out why this happened? Just started happening to me now, worked all the time. Then after a minute it worked again. Maybee google server was down?

[roskelld]

I've just started getting it too. Been working on a Chrome app and in the past 15 minutes started to get it every time I load the app. The geo location stuff isn't working, it's defaulting to my debug lat/long.

[El Dude]

Getting this too since a few weeks. Just guessing - could it be the name of the Wifi changed I / you are connected to and Google location service has no idea how to deal with the new Wifi name?

[jasan]

known bug: bugs.chromium.org/p/chromium/issues/detail?id=753242

[JohnnyQ]

I'm experiencing this now. It was working 2 hours ago and now I can't figure out why it's throwing Returned error code 403 I looked at my API dashboard and the Traffic nor Error analytics are empty. Looks like my request didn't even reach Google. Where should we look for the "warnings" you mentioned?

[Carlos_E.]

Hey @JohnnyQ , you should test this behavior on different browsers to make sure that the 403 is actually coming from chrome, head over to console.developers.google.com , your dashboard should show the state of the requests that get to the server.

[Omri Luzon]

Maybe there is an issue, but the question is from 5 months ago.

[Sajjad Ali]

yeah i agree. maybe there is an issue with google API. but i got the workaround.

[Nick Tsai]

Yep, there is only Chrome has the problem.

[Squatting Bear]

This was the problem for me, setting some restrictions in the console fixed it. Thanks!