-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sometimes geolocation no longer working (uses old endpoints) #11862
Comments
I'm able to reproduce the first screenshot in this version:
macOS version is wrong in that string though, I'm on 11.0 Beta (20A5374i) Following your steps, our geolocation fallback is working on:
with the experimental brave://flags/#enable-core-location-implementation enabled, I'm getting the most accurate result starting with 1.15.x and 1.16.x (doesn't work in 1.14.x) |
I ran through the above on Friday and tried again today but couldn't reproduce the above on Using
Using
Using
|
@LaurenWags This is likely a wontfix for Mojave but can you take a look at #10724, I think this is fixed in Nightly with the latest c87 bump. |
@rebron #10724 doesn't have a test plan so I can't be 100% sure it's working as expected. However, I can navigate to https://browserleaks.com/geo or https://html5demos.com/geo/ and geolocation works using Nightly.
|
Reproduced on
As per the discussion via Slack, geolocations seem to be using the wrong endpoints. Once you've given macOS the needed permissions for Brave to use the Location Services, you'll get the following:
Please see https://bravesoftware.slack.com/archives/C7VLGSR55/p1605674399117500 for more context. CCing @rebron @bsclifton |
So it looks like it's now working with Removing from the |
Removing |
Talking with @simonhong - we think this must be related to the build. I'll try to verify also (haven't had a chance yet, apologies) |
@bsclifton any updates on this one? Probably should figure this one out before we accidently release a build that breaks geolocation. We usually don't run through geolocation checks for minor CR/HF releases. Maybe we should add it them until we figure out the above? |
@kjozwiak I guess the problem is not specific to geolocation, rather it is something general that affects CI. I.e. it easily can hit any other feature :D posting a link to slack discussion just for context and cc @mihaiplesa |
a small chance this is related to https://github.com/brave/devops/issues/4089 |
@iefremov I've just fixed that issues and it only affected PR builds. |
This has been isolated to one of the release build nodes which had an old |
Thanks @mihaiplesa 👍 Closing this off and we'll check it with the next |
Thanks @mihaiplesa , good catch!! |
Verification PASSED on
Ensured that we're always using
Verification passed on
Verified that we're always using
Verification PASSED on
Ensured that we're always using
|
@rebron mind checking this on your end as well when you have some time? The more people that check the better as this was dependent on the nodes that were used to build the releases. Want to make sure it's working for everyone 👍 |
@kjozwiak a little late but checked this on M1 and confirmed we're using
|
Description
Starting with 1.14.x geolocation no longer works on macOS Mojave. It seems on 1.13.x and prior we were proxying thru location.brave.com, however with 1.14.x that proxy doesn't seem to be there so geolocation fails.
Note, this is working for @kjozwiak using Catalina. Additionally, @btlechowski checked Linux and Windows and geolocation is working there as well.
Steps to Reproduce
Actual result:
Location service fails:
Expected result:
Should work as it did in 1.13.86:
Reproduces how often:
easy
Brave version (brave://version info)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
cc @rebron
The text was updated successfully, but these errors were encountered: