-
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
Crash reporting prompt on release channel #1841
Comments
Note to take a look at info bar and using onboarding to set crash reporting pref. |
We may also try to be a bit more proactive - e.g. suggest sending a crashdump after an actual crash. Or anything like this to encourage the existing auditory to toggle the switch. |
P3A metric proved that almost nobody enables crash reporting on release channel. We definitely should raise the priority of this to start getting some real data from stable clients. |
@rebron WDYT about this crash reports dialog text? |
@rebron This new dialog should be visible before restore pages dialog? |
Working on this. |
@simonhong If user selects block, we still show the dialog again after future crash(es). |
fix brave/brave-browser#1841 Launch crash reporting permission ask dialog on startup after crash. Launch tab restore dialog after permission ask dialog is closed. By overriding, ShowIfNotOffTheRecordProfileBrave() is called instead of ShowIfNotOffTheRecordProfile(). ShowIfNotOffTheRecordProfileBrave() will launch crash reporting permission ask dialog and then tab restore dialog is launched after permission ask dialog is closed.
fix brave/brave-browser#1841 Launch crash reporting permission ask dialog on startup after crash. Launch tab restore dialog after permission ask dialog is closed. By overriding, ShowIfNotOffTheRecordProfileBrave() is called instead of ShowIfNotOffTheRecordProfile(). ShowIfNotOffTheRecordProfileBrave() will launch crash reporting permission ask dialog and then tab restore dialog is launched after permission ask dialog is closed.
fix brave/brave-browser#1841 Launch crash reporting permission ask dialog on startup after crash. Launch tab restore dialog after permission ask dialog is closed. By overriding, ShowIfNotOffTheRecordProfileBrave() is called instead of ShowIfNotOffTheRecordProfile(). ShowIfNotOffTheRecordProfileBrave() will launch crash reporting permission ask dialog and then tab restore dialog is launched after permission ask dialog is closed.
fix brave/brave-browser#1841 Launch crash reporting permission ask dialog on startup after crash. Launch tab restore dialog after permission ask dialog is closed. By overriding, ShowIfNotOffTheRecordProfileBrave() is called instead of ShowIfNotOffTheRecordProfile(). ShowIfNotOffTheRecordProfileBrave() will launch crash reporting permission ask dialog and then tab restore dialog is launched after permission ask dialog is closed.
Verified
Steps:
Also checked the Verification passed on
Verified the above test plan. Verified when crash reporting is disabled, the prompt is show.
Verified clicking Verification passed on
|
Casting |
Description
In dev and beta, crash reporting is on by default and folks can turn it off if they really want to. On release channel, we should ask folks if they want to send us reports. They're probably most likely to be in the right headspace for that question right after the browser has crashed — there's a motivation to send the report to prevent this specific crash from happening in future releases.
After a crash, when the browser restarts, we should ask whether to send crash reports. The possible answers should be always/yes/no/never or ideas to that effect.
Design
Show a user-blocking modal requesting permission to automatically send crash reports when the app re-opens after a crash. This dialog should take precendence over any other user-blocking dialog (e.g. the 'set Brave as default browser' dialog that occurs on 2nd launch).
"This setting" links to the crash reports item in
brave://settings
Assets
Figma: https://www.figma.com/file/pVwKlNQJU9wTVOa9tImKpo/Browser-Dialogs?node-id=36%3A810
The text was updated successfully, but these errors were encountered: