Diagnostics

Overview

The Diagnostics tab shows crash reports and stability issues from your connected services. This gives you a unified view of technical problems alongside the customer feedback that describes them.

Data sources

Diagnostics can be imported from:

• Sentry — Real-time issue syncing via webhooks
• Firebase Crashlytics — Crash alerts via Firebase Extension
• Google Play — Crash reports and ANRs via the Reporting API
• App Store Connect — Crash diagnostics (requires Admin API key role)

Diagnostic types

• Crash — Fatal errors that cause the app to terminate unexpectedly
• ANR (Application Not Responding) — The app became unresponsive for an extended period

Diagnostics list

The diagnostics list shows all reported issues, sorted by occurrence count (most impactful first). You can filter by type (Crash or ANR) and status. Each entry shows:

• Error message or signature
• Type badge (Crash or ANR)
• Status: open, resolved, or ignored
• Occurrence count
• App version and build number
• First and last seen timestamps

Diagnostic details

Click on a diagnostic entry to see:

• Full error message
• Type and current status
• Occurrence count and version information
• First and last seen timestamps
• Crash Logs — Individual crash occurrences with device model, OS version, timestamp, and full backtrace (expandable)
• Link to view the issue in the original provider (Sentry, etc.)

Managing diagnostics

You can change the status of a diagnostic entry to track resolution:

• Open — Active issue that needs attention
• Resolved — Issue has been fixed
• Ignored — Issue is known and intentionally not being addressed

Status changes from Sentry are synced automatically. When an issue is resolved or ignored in Sentry, the status updates in ReleaseTag as well.

Clearing diagnostics

To remove all diagnostic data and start fresh, go to Project Settings → Danger Zone → Clear Diagnostics. New data will continue to flow in from connected integrations.