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.

Sign up for GitHub

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

Jump to bottom

Crash reports are not enabled by default in Dev channel #3729

Closed
bsclifton opened this issue Mar 15, 2019 · 3 comments
Closed

Crash reports are not enabled by default in Dev channel #3729

bsclifton opened this issue Mar 15, 2019 · 3 comments
Assignees
@simonhong
Labels
closed/duplicate Issue has already been reported closed/invalid feature/settings priority/P2 A bad problem. We might uplift this to the next planned release.

Comments

@bsclifton
Copy link
Member

Description

Crash reporting used to be enabled by default on Developer channel builds. At some point, it became disabled by default.

Setting is found in brave://settings under Privacy and Security

Screen Shot 2019-03-14 at 11 33 47 PM

Steps to Reproduce

  1. Fresh profile
  2. Install Developer channel build
  3. Go to brave://settings

Actual result:

Automatically send crash reports to Brave is turned off

Expected result:

Automatically send crash reports to Brave should be turned on

Reproduces how often:

100%

Brave version (brave://version info)

0.63.8 Chromium: 73.0.3683.75 (Official Build) dev (64-bit)

Reproducible on current release:

  • Does it reproduce on brave-browser dev/beta builds? DEV yes, BETA no (this is not enabled by default on BETA or RELEASE)
@bsclifton
Copy link
Member Author

per @kjozwiak - setting is disabled in 0.60.17 Chromium: 72.0.3626.64
So regression happened before then

@rebron rebron added the priority/P2 A bad problem. We might uplift this to the next planned release. label Mar 15, 2019
@bsclifton
Copy link
Member Author

I ran the bisect tool on all developer channel builds, ending with 0.60.17 and none of them contained the crash reporting by default (each test was a fresh profile). I don't think this was ever enabled at all

@bsclifton
Copy link
Member Author

Closing as dupe of #1630

@bsclifton bsclifton added this to the Dupe / Invalid / Not actionable milestone Mar 15, 2019
@bsclifton bsclifton added the closed/duplicate Issue has already been reported label Mar 15, 2019
@bsclifton bsclifton mentioned this issue Mar 15, 2019
Closed
@bsclifton bsclifton removed QA/Yes needs-investigation A bug not 100% confirmed/fixed regression labels Mar 15, 2019
@bbondy bbondy removed this from the Dupe / Invalid / Not actionable milestone May 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@simonhong simonhong

Labels
closed/duplicate Issue has already been reported closed/invalid feature/settings priority/P2 A bad problem. We might uplift this to the next planned release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@bbondy @kjozwiak @bsclifton @rebron @simonhong