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

Crash reporting prompt on release channel #1841

Closed
tildelowengrimm opened this issue Oct 25, 2018 · 12 comments · Fixed by brave/brave-core#9508
Closed

Crash reporting prompt on release channel #1841

tildelowengrimm opened this issue Oct 25, 2018 · 12 comments · Fixed by brave/brave-core#9508
Assignees
Labels
design A design change, especially one which needs input from the design team OS/Desktop priority/P3 The next thing for us to work on. It'll ride the trains. QA Pass-Linux QA Pass-macOS QA Pass-Win64 QA/Test-All-Platforms QA/Test-Plan-Specified QA/Yes release-notes/include

Comments

@tildelowengrimm
Copy link
Contributor

tildelowengrimm commented Oct 25, 2018

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).

image

"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

@tildelowengrimm tildelowengrimm added design A design change, especially one which needs input from the design team design/needs-mock-up needs-mockup A feature which needs design mockup to be implemented. labels Oct 25, 2018
@tildelowengrimm tildelowengrimm added this to the 1.0 milestone Oct 25, 2018
@srirambv
Copy link
Contributor

srirambv commented Oct 25, 2018

Crash reporting is not enabled by default on Dev and Beta or any channel. #1630 is logged to enable it since we mention its enabled on the download page

cc: @rebron

@bbondy bbondy modified the milestones: 1.0, 1.x Backlog Oct 30, 2018
@rebron rebron added the priority/P4 Planned work. We expect to get to it "soon". label Nov 2, 2018
@rebron rebron modified the milestone: 1.x Backlog Feb 7, 2019
@rebron rebron removed the priority/P4 Planned work. We expect to get to it "soon". label May 5, 2020
@rebron
Copy link
Collaborator

rebron commented May 5, 2020

Note to take a look at info bar and using onboarding to set crash reporting pref.

@rebron rebron added the priority/P3 The next thing for us to work on. It'll ride the trains. label May 5, 2020
@iefremov
Copy link
Contributor

iefremov commented May 5, 2020

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.

@iefremov
Copy link
Contributor

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.

@karenkliu
Copy link

@rebron WDYT about this crash reports dialog text?

@karenkliu karenkliu removed the design/needs-mock-up needs-mockup A feature which needs design mockup to be implemented. label Mar 24, 2021
@simonhong simonhong self-assigned this Jun 18, 2021
@simonhong
Copy link
Member

simonhong commented Jul 19, 2021

@rebron This new dialog should be visible before restore pages dialog?
Oops, @karenkliu already commented about this :)

@simonhong
Copy link
Member

Working on this.
@rebron @karenkliu , With current dialog design, we give two options, block or allow.
If user selects block, we will not show this dialog again for the future crash?

@karenkliu
Copy link

@simonhong If user selects block, we still show the dialog again after future crash(es).

simonhong added a commit to brave/brave-core that referenced this issue Jul 27, 2021
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.
simonhong added a commit to brave/brave-core that referenced this issue Jul 28, 2021
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.
simonhong added a commit to brave/brave-core that referenced this issue Jul 30, 2021
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.
simonhong added a commit to brave/brave-core that referenced this issue Aug 2, 2021
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.
@simonhong simonhong added this to the 1.29.x - Nightly milestone Aug 2, 2021
@stephendonner
Copy link

stephendonner commented Aug 2, 2021

Verified PASSED using the testplan from brave/brave-core#9508 with build

Brave 1.29.45 Chromium: 92.0.4515.115 (Official Build) nightly (x86_64)
Revision 48cb2f4029b84b003719740a6cf9ca73f374a857-refs/branch-heads/4515_105@{#4}
OS macOS Version 12.0 (Build 21A5294g)

Steps:

  1. new profile
  2. launched Brave and opened several tabs
  3. checked and confirmed crash reporting is not enabled on brave://settings/privacy
  4. loaded brave://inducebrowsercrashforrealz to simulate browser crash
  5. restarted Brave
  6. confirmed crash reporting permission ask dialog was launched
  7. confirmed clicking on this settings opens brave://settings/privacy in the background (still a modal window displayed)
  8. clicked Block and confirmed tab-restore bubble was displayed
  9. clicked Allow and confirmed the tab-restore bubble was displayed
  10. confirmed crash reporting is now enabled from brave://settings/privacy
  11. also confirmed the user will see this dialog on restart, after each crash, unless they click Allow, in which it will be a silent crash-report submission (per Crash reporting prompt on release channel #1841 (comment))
default crash-reporting pref (disabled) crash reporting permission dialog this setting Block step Allow step crash-reporting pref enabled
Screen Shot 2021-08-02 at 2 36 54 PM Screen Shot 2021-08-02 at 2 36 39 PM Screen Shot 2021-08-02 at 2 51 45 PM Screen Shot 2021-08-02 at 2 36 54 PM Screen Shot 2021-08-02 at 2 37 24 PM Screen Shot 2021-08-02 at 2 37 33 PM

Also checked the Light theme

Screen Shot 2021-08-02 at 2 36 19 PM


Verification passed on

Brave 1.29.60 Chromium: 92.0.4515.131 (Official Build) beta (64-bit)
Revision 6b8d6c56ce21e38a72f7c4becb5abc1fa5134f29-refs/branch-heads/4515@{#1933}
OS Ubuntu 18.04 LTS

Verified the above test plan.

Verified when crash reporting is disabled, the prompt is show.
Verified clicking settings opens brave://settings/privacy

image image

Verified clicking Allow enables crash reporting
image

Verified clicking Block disables crash reporting
image

Verified dark mode:
image


Verification passed on


Brave | 1.29.60 Chromium: 92.0.4515.131 (Official Build) beta (64-bit)
-- | --
Revision | 6b8d6c56ce21e38a72f7c4becb5abc1fa5134f29-refs/branch-heads/4515@{#1933}
OS | Windows 10 OS Version 2009 (Build 19043.1165)


Verified when crash reporting is disabled, the prompt is shown.
Verified clicking settings opens brave://settings/privacy

image image

Verified clicking Allow enables crash reporting
image

Verified clicking Block disables crash reporting
image

Verified Dark mode
image

@stephendonner
Copy link

Casting QA/Test-All-Platforms label because it'd be great to have eyeballs across platforms, here, given the importance of the data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design A design change, especially one which needs input from the design team OS/Desktop priority/P3 The next thing for us to work on. It'll ride the trains. QA Pass-Linux QA Pass-macOS QA Pass-Win64 QA/Test-All-Platforms QA/Test-Plan-Specified QA/Yes release-notes/include
Projects
None yet
Development

Successfully merging a pull request may close this issue.

10 participants