As a developer I want to receive crash reports

[vesta0]

Why/User Benefit/User Problem

As a developer, I want to receive crash reports when Fenix crashes.

Dependencies

• Crash reporting #304 (Resolved / Merged)

Acceptance Criteria (how do I know when I’m done?)

• When Fenix crashes in application code or native A-S code, a crash report is sent to Sentry
• When Fenix crashes in GeckoView, a crash report is sent to Socorro
• When the user has opted out from sending crash reports (via settings, specified in another user story) no crash reports should be sent. This is only so for Sentry and Soccoro reports. Android will still send reports to the Google Play Store, and that is controlled byt he user at an Android level, not in Fenix.
• Crash reports should contain enough data to resolve or investigate a crash (ideal situation, but due to the nature of reports, this is simply not always the case)

┆Issue is synchronized with this Jira Task

[sblatz]

I noticed we do not have any UX for this. I'm happy to use a Focus-inspired crash page similar to the one found below, but we will need to make a couple changes:

1. New copy for the description since we're saving history and not a private browser
2. How "restoring" a session should look (likely a restore session button similar to close tab, with copy that reflects this)

@mheubusch for copy, @lime124 for UX.

Current Implementation

Let's also take this ticket into account for UX.

[lime124]

@topotropic since there are session related questions. and thanks sblatz for bringing this up! :)

[sblatz]

What I'm using for now:

[cadeyrn]

a quick note: Both buttons have the same style in your screen. In Firefox for the desktop you have a primary action and a secondary action in about:tabcrashed, both buttons are differently styled. I don't know if you want to do something similar in Fenix. Maybe this is something to consider. ;-)

[sblatz]

Updated the buttons as so for now:

[topotropic]

@brampitoyo I think you are working on this atm, can you have a look?

[brampitoyo]

@topotropic Thanks for pinging me on this. I will have a look at this issue as a part of designing the messaging system (which @shorlander has designed the framework of).

@sblatz Stay tuned for some design! I will first make sure that whatever we use here will look great with the rest of our in-product messaging pages (e.g. 404, SSL errors, malware warnings, etc.)

[sblatz]

@bbinto, @vesta0: can I get clarification on what Telemetry events we want for this?

[bbinto]

@sblatz - added info here #1040

[brampitoyo]

The UX has been posted on #1102.

[sblatz]

This is blocked on #1067 so that I have a baseline for telemetry events.

[sblatz]

This feature has been complete for a few days now. The only thing missing from the user story is the telemetry which @boek is helping me out with!

In the future, we should likely break out Telemetry stories so that they don't block an entire feature being QA ready.

[sblatz]

Per a conversation with Betty, I created a telemetry user story so that this could move to QA.

[sv-ohorvath]

This is verified by QA. There are new issues logged for the bugs found, I'll close this ticket.