-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Enable Crash reporting by default for Dev and Nightly (0.63 and later) #1630
Comments
First run flow is a great place to put the notification. It could also go on the download page next to the download button. |
Text is now live on the download pages for dev and beta, which ✅ the privacy review. We should be fine to actually turn this on now. |
Prompt for release builds is in #1841. |
@tomlowenthal should we mention |
I added it to the beta channel but not dev for two reasons. Number one, honestly was length — the dev text is already quite long. Number two was that I fully expect people using dev to go into their settings immediately after install and touch every button, switch, and knob. I very much doubt that anyone's going to compare the two pages and reach the conclusion that crash reporting can't be disabled on dev. And if folks are scared away from dev for that reason, I suspect they'd be happier on beta anyway. 🤷🏻♂️ |
Total number of users for dev and for beta are running the same right now. |
I think we'll want to run some marketing efforts to get Beta 10x the size as dev at some point. |
Per #3729 - I verified this was never actually enabled |
@simonhong FYI - I just added a test plan (in case you wanted to verify it) 😄 |
Verification passed on
Verification passed on
Verified passed with
|
Test plan
Automatically send crash reports to Brave
is enabledDescription
Crash reporting should be enabled by default on Dev and Nightly so that we can get reports on whats causing the crashes. This should also be informed to the user on the welcome page probably on the first page as a note or as an option at the end. Preferably on the first view of the welcome page as some users might just click skip welcome tour and might not see it if its at the end.
cc: @bbondy @rebron @kjozwiak @bsclifton
The text was updated successfully, but these errors were encountered: