Crashes

Check crash data and focus on the issues affecting real users.

See Whether Stability Is Getting Better

Crashes summarizes the crash metrics available through App Analytics. It helps you see whether crashes are going up, how many devices are affected, and whether a particular app version needs a closer look.

This is a view of reported metrics. For an individual crash's feedback and investigation details, also check TestFlight and your usual debugging tools.

Make Sure Reports Are Available

Link the project to your App Store Connect app in Basic Information and configure account access in Settings. App Analytics reporting needs to be available too.

If the page says analytics or crash data is unavailable, follow that message and check App Analytics. An unavailable report doesn't mean your app is magically crash-free.

Use Refresh to update the available information after a build has been out in the wild for a while.

Read the Overview

The summary includes total crashes, affected devices, and sessions where those metrics are present. The crash-free rate is shown when the required session data is available.

Read counts and rates together. More crashes during a much busier period can mean something very different from more crashes while usage stays flat.

The trend chart helps you see when a change began, and the version breakdown helps narrow the investigation down to particular releases.

Decide What to Investigate

If crashes rise after a release, compare the timing with the changes you shipped and the feedback coming from users. You might need to reproduce a new flow, dig into a migration, or chase down a device-specific problem.

Record the evidence in a task so the investigation has a clear starting point. The metrics can tell you where to look, but they won't find the underlying bug for you.

After a fix has shipped and fresh reports arrive, come back and see whether the pattern improves. Keep report coverage in mind when comparing the old and new versions.