Release health

App crash rate by version.
Spot a bad release.

Storewatch compares your newest iOS version with the one before it: crash rate, launch time, hangs, memory and disk writes, taken from Apple’s own reports. It turns red only when Apple flags a regression or the crash rate clearly rose.

3 days freeOne-time purchaseLoved by developers

The Storewatch dashboard in the sample app with the Crash rate tile selected: 0.27%, up 104.7% on the previous 28 days, and the chart jumping from about 0.2% to 0.45% right after the Calorie Tracker 4.3 release.

Crashes up?
You’ll know.

When the newest version’s crash rate clearly rises, Insights says so, with both rates side by side.

The Retention insights for Calorie Tracker in the sample app: “Version 4.3 crashes more than 4.2” (0.46% of sessions vs 0.19%) and “Launch time got worse in 4.3”, with Storewatch’s chat answering Ask about this: two reviews that mention crashes when scanning a barcode, and what to check next.

On the dashboard.
For every app.

A crash rate tile for all apps, and a warning on any app whose newest release looks worse.

The Usage screen for Calorie Tracker in the sample app: sessions, installations, deletions and crash rate by week, with the crash rate chart rising after version 4.3 and a weekly table of crash rate.

Check the next one
before you submit.

The Pre-submission check finds an empty What’s New, text over limits, a missing demo account or the wrong build.

The Releases screen for Calorie Tracker: Release health for version 4.3 against 4.2, then TestFlight builds and a Pre-submission check listing an empty What’s New, text limits and listing problems.

Where do the crash and performance numbers come from?

Both come from Apple, and both depend on users who share analytics with developers. Storewatch doesn’t add an SDK to your app and measures nothing itself.

NumberSourceHow Storewatch uses it
Crash rateApple’s analytics reports: crashes and sessions, by app versionCrashes divided by sessions for each version. Shown as “worse” only with at least 100 sessions on both versions, a rise of at least a quarter, and at least 0.05 percentage points.
Launch time, hang rate, scroll hitchesApple’s power and performance metrics for the appThe typical user (50th percentile), on all iPhones when Apple has it. Lower is better.
Peak memory, memory when suspended, disk writesThe same Apple metricsLatest version against the previous one. “Better” means at least 15% lower.
Battery, on screen and in the backgroundThe same Apple metricsThe same comparison, shown when Apple reports it.
RegressionsApple’s own flags in those metricsA row is red when Apple lists a regression for the latest version, with Apple’s sentence beside it.

What “worse” means

Storewatch doesn’t colour a row red for small wobbles. A crash rate counts as worse only when it clearly rose, and a performance row only when Apple itself reports a regression. A row Apple says is trending up is marked as creeping up, not worse. With too little data a row says so instead of guessing.

What it can’t show

Apple measures power and performance for iOS apps only, and only from users who agreed to share diagnostics and analytics, so a new or small app may see little or nothing. Apple also applies privacy thresholds, which hide numbers when too few users contribute. The performance numbers are read once a day; Refresh re-reads them unless they were checked in the last five minutes. For how Apple’s analytics reports are requested and delivered, see the Analytics Reports API guide.

Questions, answered.

How do I check crash rate by app version?

Open Releases for the app in Storewatch. Release health lists the newest version against the one before for crash rate and Apple’s performance numbers. Apple’s own Xcode Organizer and App Store Connect show crashes too; Storewatch puts the comparison next to your sales and reviews.

What counts as a high crash rate?

There is no official line. Storewatch calls a rise real when the newest version has at least 100 sessions, the rate is up at least a quarter and at least 0.05 percentage points. At double the old rate the insight becomes a problem.

Why is Release health empty?

Apple has too little data for the app. The numbers come from users who share analytics with developers, and only iOS apps get Apple’s performance metrics. Analytics reports also need to be turned on for the app.

Does Storewatch add anything to my app?

No. It reads Apple’s reports through your App Store Connect key. There’s no SDK to add.

Does it show crash logs and stack traces?

No. Storewatch shows rates and trends by version and tells you which one got worse. For the stack traces, open Xcode’s Organizer.

Made by Alex, the developer of Storewatch. Last updated 21 November 2026.

Catch a bad release early.

3 days freemacOS 15 or later on Apple silicon