When the app hits an error or crash, offer the user the chance to submit an
auto-generated bug report with their own comments. All debug info is shown before sending,
with a disclaimer that it may contain PII. Submission is strictly opt-in / user-initiated
(F-Droid-safe, see #16). The server side is #11.
Spec
When the app encounters an error or a crash, it should offer the user the opportunity to
submit an automatically generated bug report along with comments on the issue. All debug
information should be displayed to the user so they can see what they are submitting. It
should also contain the disclaimer that the debug information may contain personally
identifiable information.
Breakdown
#32 — error/crash capture + "Report a problem" entry point
A crash produces a saved report offered for review on next launch; a manual entry point exists.
The user sees the full payload + PII disclaimer, can add comments, and explicitly submits
or discards.
Nothing is transmitted without explicit user action.
Notes
Server ingest / anonymize / storage / publish is #11. Keep captured data minimal — scrubbing
also happens server-side (#34).
## Summary
When the app hits an error or crash, offer the user the chance to submit an
auto-generated bug report with their own comments. All debug info is shown before sending,
with a disclaimer that it may contain PII. Submission is **strictly opt-in / user-initiated**
(F-Droid-safe, see #16). The server side is #11.
## Spec
When the app encounters an error or a crash, it should offer the user the opportunity to
submit an automatically generated bug report along with comments on the issue. All debug
information should be displayed to the user so they can see what they are submitting. It
should also contain the disclaimer that the debug information may contain personally
identifiable information.
## Breakdown
- [ ] #32 — error/crash capture + "Report a problem" entry point
- [ ] #33 — report review & opt-in submit (data display, PII disclaimer, comments, transport)
## Acceptance criteria
- A crash produces a saved report offered for review on next launch; a manual entry point exists.
- The user sees the full payload + PII disclaimer, can add comments, and explicitly submits
or discards.
- Nothing is transmitted without explicit user action.
## Notes
Server ingest / anonymize / storage / publish is #11. Keep captured data minimal — scrubbing
also happens server-side (#34).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
When the app hits an error or crash, offer the user the chance to submit an
auto-generated bug report with their own comments. All debug info is shown before sending,
with a disclaimer that it may contain PII. Submission is strictly opt-in / user-initiated
(F-Droid-safe, see #16). The server side is #11.
Spec
When the app encounters an error or a crash, it should offer the user the opportunity to
submit an automatically generated bug report along with comments on the issue. All debug
information should be displayed to the user so they can see what they are submitting. It
should also contain the disclaimer that the debug information may contain personally
identifiable information.
Breakdown
Acceptance criteria
or discards.
Notes
Server ingest / anonymize / storage / publish is #11. Keep captured data minimal — scrubbing
also happens server-side (#34).