Skip to content
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

Geolocation not using correct service #12952

Closed
LaurenWags opened this issue Nov 30, 2020 · 1 comment
Closed

Geolocation not using correct service #12952

LaurenWags opened this issue Nov 30, 2020 · 1 comment

Comments

@LaurenWags
Copy link
Member

Description

Sometimes builds do not use the correct service (location.brave.com) for geolocation and instead use location.services.mozilla.com.

Steps to Reproduce

  1. Navigate to https://browserleaks.com/geo or https://html5demos.com/geo/.
  2. Allow site to know your location from the bubble
  3. Wait

Actual result:

Location is not identified. If you use Little Snitch, Charles Proxy, etc you will see that it is trying to use location.services.mozilla.com.

Expected result:

Should use location.brave.com for geolocation.

Reproduces how often:

easily if you get a build that is affected

Brave version (brave://version info)

1.19.39, 1.19.41 on both intel and arm64 macOS although when this happens it is not specific to macOS, it can occur on any OS

Version/Channel Information:

  • Can you reproduce this issue with the current release? intermittently yes
  • Can you reproduce this issue with the beta channel? intermittently yes
  • Can you reproduce this issue with the nightly channel? intermittently yes

Other Additional Information:

  • Does the issue resolve itself when disabling Brave Shields?
  • Does the issue resolve itself when disabling Brave Rewards?
  • Is the issue reproducible on the latest version of Chrome?

Miscellaneous Information:

cc @rebron @kjozwiak

@kjozwiak
Copy link
Member

kjozwiak commented Dec 1, 2020

Duplicate of #11862. We can either close this one off or close the other one and keep this one. However, #11862 has more info/context. @rebron I'll let you decide which issue you prefer leaving opened 👍

@bsclifton bsclifton self-assigned this Dec 1, 2020
@rebron rebron added the closed/duplicate Issue has already been reported label Dec 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants