1931083 - (Firefox Android) SUMO Article for "Automatically send crash reports" setting [V136]

Status: RESOLVED FIXED

(support.mozilla.org :: Knowledge Base Content, task)

Description

[athomas]

Product (ensure to select only one product for each ticket. If your request involves multiple products, file an individual Bugzilla for each)

Choose one below and delete others. [REQUIRED]
Firefox for Android

Select the type of request.

KB content update/ new content
In-product link request

Please summarize the request, emphasizing any user-facing changes. Include historical context or background information if it helps users understand the new features or changes. [REQUIRED]

Add a SUMO article that can be pointed to from the new preference to "Automatically Send Crash Reports," so that users can make an informed decision on whether to toggle on or off. It should include:

• What data is included in a crash report
• How we use crash reports
• How users can choose to send a crash report or not (we should include both information on the setting to automatically send and details on what happens if that settings is turned off - we ask after a crash if we can send a report)

##Are the user-facing changes mentioned above for the production release, or is the feature/change experimental/ beta? (Production, Experimental or Beta) [REQUIRED]
Yes. There will be a new option added to settings to "Automatically Send Crash Reports" which includes a "Learn More" link that points to this article

Are the new features or changes region-specific? Are they going to be released in a gradual rollout? [REQUIRED]

All regions & locales

Please indicate if this is an on- or off-train release [REQUIRED]

Yes

What is the anticipated release date? [REQUIRED]

The article can launch in 134 or 135. Feature will launch in 134, but learn more links may not be added until 135 unless ready earlier

Does the content need to be published prior to the release date? If so, when? [REQUIRED]

No

Does the content need to be localized in any languages outside of EN-US? If yes, please indicate which languages. [REQUIRED]

Yes, all locales

Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]

https://mozilla-hub.atlassian.net/browse/FXDROID-2910
https://docs.google.com/document/d/1xAEnNDIE206CWvSZS1KwXDnXsCtOPO1ef3vbR4W_FnA/edit?tab=t.0

Please include links to any design assets, visuals, figma files, etc. [REQUIRED]

https://docs.google.com/document/d/1xAEnNDIE206CWvSZS1KwXDnXsCtOPO1ef3vbR4W_FnA/edit?tab=t.0

Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]

Does the content need approval before publishing? If yes, identify the one approver responsible for this task.

Yes. It will need sign-off from Jennifer Johnson (legal), Bobby Holley (project sponsor), TBD engineer, Ashley Thomas

Comment 1

[Chris Peterson [:cpeterson]]

Jeff says he aims to ship the new crash reporter in Fx 134.

Comment 2

[Chris Peterson [:cpeterson]]

We have an existing article about Android's crash reporting.

https://support.mozilla.org/en-US/kb/how-send-crash-report-firefox-android

Note that this article's path mentions a "Troubleshooting" level, but clicking it opens a 404 page: https://support.mozilla.org/en-US/products/mobile/troubleshooting

Home / Firefox for Android / Troubleshooting / How to send a crash report on...

Comment 3

[Lucas Siebert]

Task link in the Asana Content Roadmap: https://app.asana.com/0/1203460865189761/1208786915392990/f

Comment 4

[Chris Peterson [:cpeterson]]

Android sends crash reports to Mozilla's "crash-stats" service and third-party service Sentry.

Android also sends "crash pings", mini crash reports that don't include any PII:

https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/data/crash-ping.html

Since crash pings don't include PII, Firefox doesn't ask for user permission to submit. Users can opt out of crash pings by opting out of all telemetry ("Allow Firefox to send technical and interaction data to Mozilla").

Comment 5

[Chris Peterson [:cpeterson]]

Attachment: Sentry_crash_info.png

Here's a screenshot of the information sent in a Sentry crash report.

Comment 6

[Chris Peterson [:cpeterson]]

Unlinking crash reporter v2 bug 1932724 because this article update is about the automatic submission setting and the crash report contents, not documenting the new crash reporter dialog or homepage card.

Comment 7

[Lucas Siebert]

In-product link: https://support.mozilla.org/1/mobile/%VERSION%/%OS%/%LOCALE%/mobile-crash-reports
Placeholder article: https://support.mozilla.org/en-US/kb/how-send-crash-report-firefox-android
Guide: https://support.mozilla.org/en-US/kb/a-guide-to-linking-to-support-articles#w_in-product-links-to-sumo

Comment 8

[Chris Peterson [:cpeterson]]

Now targeting Fx 136

Comment 9

[Chris Peterson [:cpeterson]]

Correction: Android and iOS (bug 1931079) both plan to ship the new "Automatically send crash reports" setting in Fx 135.

Comment 10

[Lucas Siebert]

Draft: https://docs.google.com/document/d/1_2tFg2SQVIeBL7bfSBjD8Et9SDVj-Y9w5HV49A2g9Uk/edit?tab=t.0

Comment 11

[Lucas Siebert]

The draft is ready for the first Product review! Here’s the link: https://docs.google.com/document/d/1_2tFg2SQVIeBL7bfSBjD8Et9SDVj-Y9w5HV49A2g9Uk/edit?tab=t.0

Comment 12

[Chris Peterson [:cpeterson]]

Note: while the "Automatically send crash reports" functionality is shipping in V135, the setting's "Learn more" link isn't shipping until V136.

Comment 13

[Alice Wyman]

(In reply to Chris Peterson [:cpeterson] from comment #2)

We have an existing article about Android's crash reporting.

https://support.mozilla.org/en-US/kb/how-send-crash-report-firefox-android

Note that this article's path mentions a "Troubleshooting" level, but clicking it opens a 404 page: https://support.mozilla.org/en-US/products/mobile/troubleshooting

Home / Firefox for Android / Troubleshooting / How to send a crash report on...

The same thing happens for certain Firefox for desktop articles such as https://support.mozilla.org/en-US/kb/troubleshoot-firefox-crashes-closing-or-quitting and https://support.mozilla.org/en-US/kb/firefox-stuck-troubleshoot-mode which are still listed under the "Troubleshooting" topic: https://support.mozilla.org/en-US/products/firefox/troubleshooting
The "Troubleshooting" topic no longer exists. Related github issue (?) https://github.com/mozilla/sumo/issues/1915 Manually migrate remaining topics to the new taxonomy

Comment 14

[Alice Wyman]

(In reply to Chris Peterson [:cpeterson] from comment #2)

We have an existing article about Android's crash reporting.

https://support.mozilla.org/en-US/kb/how-send-crash-report-firefox-android

I set up a "Needs change" entry for the existing How to send a crash report on Firefox for Android article and referenced this bug.

Note that this article's path mentions a "Troubleshooting" level, but clicking it opens a 404 page: https://support.mozilla.org/en-US/products/mobile/troubleshooting

Home / Firefox for Android / Troubleshooting / How to send a crash report on...

After I edited the article metadata to add the "Needs change" entry, I noticed that the topic is now https://support.mozilla.org/en-US/products/mobile/performance-and-connectivity

Comment 15

[Alice Wyman]

The Crash reports in Firefox for Android article was recently updated - see https://support.mozilla.org/en-US/kb/how-send-crash-report-firefox-android/history (The Feb 25, 2025 revision comment by Dayani referenced this bug.)

Should this bug be reassigned to Dayani if any other changes are needed or should it be resolved as fixed?

Comment 16

[Dayana]

(In reply to Alice Wyman from comment #15)

The Crash reports in Firefox for Android article was recently updated - see https://support.mozilla.org/en-US/kb/how-send-crash-report-firefox-android/history (The Feb 25, 2025 revision comment by Dayani referenced this bug.)

Should this bug be reassigned to Dayani if any other changes are needed or should it be resolved as fixed?

Hi Alice, I have reassigned the bug to Dayani. Please let her know if you submit any changes that need review.

Comment 17

[Ryan VanderMeulen [:RyanVM]]

Can we close this bug?

Comment 18

[Chris Peterson [:cpeterson]]

We can close this bug. We're tracking some content updates to this article in bug 1958999.