Skip to main content

Issues and Crashes

The Issues view groups repeated reports so you can measure impact without treating every occurrence as a separate problem. Crash reports and issues reported through the SDK can be investigated from this product area.

The Issues view with impact charts and grouped reports

Prioritize an issue​

Use the summary charts to compare Issues, New Issues, and Affected Devices over the selected date range. Then use the table to compare groups:

  • Devices shows how widely the issue affects installations.
  • Issues shows the number of matching occurrences.
  • First Seen helps identify when the problem began.
  • Last Seen shows whether it is still happening.
  • Status records its triage state.

A high occurrence count on one device can mean something different from a lower count spread across many devices. Check both values before opening a group.

Track status​

Issue and crash groups support these statuses:

StatusSuggested use
NewThe group has not yet been triaged.
OpenThe group is accepted and needs attention.
In ProgressSomeone is actively investigating or fixing it.
ResolvedA fix or resolution is available but may still need verification.
ClosedWork and verification are complete.
MutedKeep the group without treating new occurrences as active work.
InvalidThe group is not an actionable product problem.

Developers and administrators can update status from the list or group detail. Agree on status conventions within your team so filters and counts remain meaningful.

Inspect a group​

Open a group to see:

  • occurrence and affected-device totals;
  • first- and last-seen times;
  • issue activity and affected-device charts;
  • breakdowns by device, operating system, and application version;
  • a representative report or stack trace;
  • symbol status and upload actions for crashes.

Use the previous and next controls above the report to move through individual occurrences in the group. Select View logs to open an occurrence in its device timeline and inspect the surrounding events.

Select View all devices to open the dedicated affected-devices list. It shows each installation's environment, occurrence count, and latest matching report, subject to the active date range and filters.

Merge duplicate groups​

An administrator can merge two issue groups or two crash groups when they represent the same underlying problem. Bugfender chooses the group with more occurrences as the canonical group and combines the reports from both.

Irreversible merge

A merge cannot be undone. Confirm that both groups represent the same problem and have the same report type before proceeding.

Triage workflow​

  1. Set a date range that covers the suspected release or incident.
  2. Filter by report type, status, application version, or identifying text.
  3. Compare affected devices and occurrences.
  4. Open the group and inspect its charts, environment breakdown, and individual reports.
  5. Open a representative occurrence in Logs.
  6. Check the affected application versions.
  7. Update the status as your team investigates and resolves the problem.
  8. Merge duplicate groups only after confirming they have the same cause.

For readable native stack traces, upload the debug symbols or mapping files required by your platform.