Crashes and error monitoring

Inspect reported errors, group recurring failures and verify fixes against the affected app build.

Before you start

Configure error reporting in the app. If using Firebase reports, connect and map Firebase separately. SmartLinks SDK reports and Firebase reports have different collection paths.

Step by step

1. Open Crashes & Errors for the intended app.
2. Review Stability Trend, Distribution and Active Error Groups.
3. Select an error group to inspect its message, stack trace and available version/device context.
4. Separate repeated instances of one issue from distinct errors.
5. Create or update a Concern with reproduction steps and the affected version/build.
6. Implement and test the fix in your development workflow, then release through your normal approval process.
7. Compare new reports from the fixed build with the earlier affected build before closing the issue.

Confirm it worked

A controlled, non-sensitive test error reaches the correct app report. A claimed fix is supported by a verified build and subsequent monitoring, not merely a “resolved” label.

Troubleshooting

Check error hooks, network access, key scope and Firebase mapping if data is absent. No reported crashes is not proof of a crash-free app. Redact user paths, tokens and personal data before sharing stack traces publicly.

Related: Integrations, Concerns.