Closed Bug 1610306 Opened 6 years ago Closed 6 years ago

HTML5 Geolocation Not Working Firefox 72.0.1 - Mozila Firefox for Ubuntu

Categories

(Core :: DOM: Geolocation, defect)

72 Branch
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: ravirupapara, Unassigned)

References

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.108 Safari/537.36

Steps to reproduce:

navigator.geolocation.getCurrentPosition(position => {

console.info(position)
}, error => {
console.error(error)
})

Running this basic code snippet in the console returns a PositionError object with the message "Unknown error acquiring position"

about:config "geo.wifi.uri" is set to

https://www.googleapis.com/geolocation/v1/geolocate?key=%GOOGLE_API_KEY%

The code snippet is tested in Chrome/IE and works as expected.

It works If I changed geo.wifi.uri to https://location.services.mozilla.com/v1/geolocate?key=test. But this is not giving me the exact location.

It would be appreciated if anyone could help me out. Thanks.

Actual results:

"Unknown error acquiring position"

Expected results:

Should return the correct location with lat long

i can confirm that i get a 429 http response from the google geolocation server when testing with builds provided by ubuntu - mozilla builds do work though (both with https://www.googleapis.com/geolocation/v1/geolocate?key=%GOOGLE_API_KEY% set).
different api keys seem to be used, so perhaps this is rather something to get on ubuntu's radar?

Unfortunately not working for me. Are there any other suggestions?

the problem is also apparent on arch linux according to https://old.reddit.com/r/firefox/comments/esejw0/location_services_problem/

Does anyone know where GOOGLE_API_KEY value is set? It's not set as an env var.

Is it per-user or a shared key for all installations?

The priority flag is not set for this bug.
:willkg, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(willkg)

I've been following this bug since it was reported. For what it's worth, the latest update (to v. 73.0.1) fixed it for me.

I think it's this issue in Launchpad:

https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1860830

I think this is a downstream issue and I suggest following up there.

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Flags: needinfo?(willkg)
Resolution: --- → INVALID
See Also: → 1622863
You need to log in before you can comment on or make changes to this bug.