-
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
Crash reporting connects to clientservices.googleapis.com on startup #3816
Crash reporting connects to clientservices.googleapis.com on startup #3816
Comments
@tomlowenthal Do you know the full URL? I think we have a network audit in CI so not sure why it wouldn't catch it. |
I think only Nightly, but I didn't reinstall Dev yesterday to check. It's not a behavior I've seen before, but I think the last time I tested was about a week ago with Dev. I don't have the URL because my firewall couldn't get that out of the HTTPS connection. |
Potential sources:
|
OK according to PJ it's |
I think this happened by brave/brave-core#1985. |
Re-opened with C74 revert |
Assuming @LaurenWags and myself can check using Little Snitch to make sure we're not connecting to |
@kjozwiak @srirambv - Fiddler works really well on Win/Linux https://www.telerik.com/download/fiddler @btlechowski @srirambv - Test plan specified here: brave/brave-core#2095 Let me know if you have any questions. |
Edit: Below findings are a know issue: #1947 On Windows 10 x64, Brave connects to Steps:
URLs:
Tested on
|
Verification passed on
Used test plan from brave/brave-core#2095 Verification PASSED on
Verified passed on
Verification passed on
|
@LaurenWags if the above worked for you, can you label this as |
Crash reporting reaches out to clientservices.googleapis.com. Discovered when crash reporting was enabled by default in Nightly channel
Original issue description
Just installed Version 0.64.7 Chromium: 73.0.3683.75 (Official Build) nightly (64-bit).
The text was updated successfully, but these errors were encountered: