(Firefox iOS) SUMO Article for "Automatically Send Crash Reports" setting [V136]
Categories
(support.mozilla.org :: Knowledge Base Content, task)
Tracking
(Not tracked)
People
(Reporter: athomas, Assigned: lsiebert, NeedInfo)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
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 iOS
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]
135
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]
Automatic crash reporting exists today. Here's the ticket to add the option to not have them sent automatically https://mozilla-hub.atlassian.net/browse/FXIOS-10465
Please include links to any design assets, visuals, figma files, etc. [REQUIRED]
Design for setting: https://www.figma.com/design/a0vLe1jbZMVNBbL3pxBBo7/Settings%3A-ToS---DAU-Opt-out?node-id=6447-12621&t=HCy9nIfIpT42SJa5-4
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
Updated•3 months ago
|
Assignee | ||
Comment 1•3 months ago
|
||
Task link in the Asana Content Roadmap: https://app.asana.com/0/1203460865189761/1208786915392992/f
Comment 2•2 months ago
|
||
Alex will update Firefox iOS to link to this new article in iOS Jira ticket https://mozilla-hub.atlassian.net/browse/FXIOS-10739
Comment 3•2 months ago
|
||
Here's a screenshot of the information that Firefox iOS sends in crash reports to Apple's App Store.
The reports also include a code stack trace, but no user PII, so Firefox doesn't ask for user permission to submit. Users can opt out of crash pings by opting out of all telemetry ("Send usage data" is the current setting name, but something like "Technical and interaction data" will be the new setting name).
Comment 4•2 months ago
|
||
Here's a screenshot of the information sent in a Sentry crash report.
Assignee | ||
Comment 5•2 months ago
•
|
||
Updated•2 months ago
|
Assignee | ||
Comment 6•27 days ago
|
||
(In reply to Lucas Siebert from comment #5)
In-product link: https://support.mozilla.org/1/mobile/%VERSION%/%OS%/%LOCALE%/mobile-crash-reports
Placeholder article: https://support.mozilla.org/en-US/kb/crash-reports-pref
Guide: https://support.mozilla.org/en-US/kb/a-guide-to-linking-to-support-articles#w_in-product-links-to-sumo
I realized it might make more sense to have dedicated crash report articles for Android and iOS. For iOS, this would mean the in-product link changes to: https://support.mozilla.org/1/mobile/%VERSION%/%OS%/%LOCALE%/ios-crash-reports.
Would it still be possible to make that change in the code? If it’s too late, I can stick with a single article for “mobile (Android+iOS)” — totally fine either way!
Assignee | ||
Comment 7•27 days ago
|
||
The draft is ready for the first Product review! Here’s the link: https://docs.google.com/document/d/14QdX0ZuB8djj_rE1k1OS8g2kHYLt7xidX9ZArIzXqZM/edit?tab=t.0
Comment 8•27 days ago
•
|
||
(In reply to Lucas Siebert from comment #6)
I realized it might make more sense to have dedicated crash report articles for Android and iOS. For iOS, this would mean the in-product link changes to: https://support.mozilla.org/1/mobile/%VERSION%/%OS%/%LOCALE%/ios-crash-reports.
Would it still be possible to make that change in the code? If it’s too late, I can stick with a single article for “mobile (Android+iOS)” — totally fine either way!
SGTM. If you recommend separate Android and iOS articles, we can still the iOS code to point a new article. I filed some bugs:
Comment 9•27 days ago
|
||
Note: while the "Automatically Send Crash Reports" functionality is shipping in V135, the setting's "Learn more" link isn't shipping until V136.
Assignee | ||
Comment 10•8 days ago
|
||
NOTE: The in-product redirect details for this article have been updated in coordination with Chris P. Here are the new details:
In-Product link: https://support.mozilla.org/1/mobile/%VERSION%/%OS%/%LOCALE%/ios-crash-reports
Placeholder article: https://support.mozilla.org/en-US/kb/ios-crash-reports-pref
Guide: https://support.mozilla.org/en-US/kb/a-guide-to-linking-to-support-articles#w_in-product-links-to-sumo
Description
•