Crash reporting for iOS & Android, from stack trace to root cause
Every crash arrives symbolicated, with the logs from the minutes before it, grouped into a short list of issues and summarised by AI. Let your AI agent investigate over MCP, and get alerted the moment crash-free sessions drop.
Included in every plan, including FREE · iOS, tvOS & Android · Hosted in Switzerland
See the minutes before every crash
A stack trace tells you where the app crashed. The activity log tells you why. Each crash report includes what happened in the app right up to the crash.
- Stack traces at the moment of the crash, with the crashing thread highlighted.
- Symbolication on the device for crash-relevant iOS frames, plus dSYM and ProGuard/R8 mapping uploads.
- Structured activity logs: console logs with levels and domains, network requests, connectivity changes, memory warnings and app state changes.
- Current screen, plus CPU and memory averages for the session.
- App, OS and device details, an optional user identifier and your own attachment of up to 100 KB.
AI that explains crashes, and agents that investigate them
Get a quick explanation of every crash group in the Dashboard, or hand the whole investigation to the AI agent you already use.
AI crash summaries
Every crash group gets a concise summary of what is going wrong, written from its latest crash report. The model runs on Appelium’s own infrastructure in Zürich, so your crash data is not sent to a third-party AI provider.
The app crashes when ProfileFragment resumes before the user profile has loaded, because profile is still null at that point.
Root-cause analysis with your AI agent
applyVoucher then reads a cart that is already empty. Guarding against the empty cart in CheckoutViewModel fixes it.Connect Claude, Copilot or Cursor to your crash data. Read the MCP documentation →
Know the moment stability drops
Follow crash-free sessions for every app and version, and let Appelium alert your team when the rate falls below your threshold.
- Excellent
- Good
- Fair
- Poor
- Unacceptable
- Crash-free sessions trends per application and app version.
- Your own threshold, monitored for each of your applications.
- Slack, Microsoft Teams and Opsgenie notifications for the team on call.
- Automatic recovery: alarms close by themselves once the rate is back above the threshold.
Release Rollout Health compares the crashed foreground sessions of a new release with the previous one, while the rollout is still small.
Learn more about release rollout health →Up and running in minutes
Enable crash reporting when you start the SDK, then upload your symbol files from CI. Everything else is optional.
AppeliumFeedback.start(
apiKey: "YOUR_API_KEY",
crashReporting: .enabled()
)
if AppeliumFeedback.hasCrashedInLastSession {
// Show a recovery message
}AppeliumFeedback.start(
apiKey = "YOUR_API_KEY",
application = this,
crashReporting = CrashReportingConfiguration.Enabled()
)
if (AppeliumFeedback.hasCrashedInLastSession) {
// Show a recovery message
}Guides for iOS, tvOS and Android, and the symbol files REST API.
Built to stay out of your way
Off by default
Nothing is collected until you enable it. No IP addresses are processed, and data is never shared with third parties.
Debugger aware
Crash reporting pauses while a debugger is attached, so it never interferes with your debugging session.
Non-fatal errors & ANRs
Report handled errors with one call. A main thread blocked for more than 5 seconds is reported automatically. Explore error reporting
Performance first
Compact payloads and efficient capture keep the SDK lightweight in your users’ hands.
Frequently asked questions
What does an Appelium crash report contain?
Each report contains the stack traces at the moment of the crash with the crashing thread highlighted, the activity logs leading up to it (console logs, network requests, connectivity changes, memory warnings and app state changes), the screen that was visible, CPU and memory averages for the session and the app, OS and device details. You can add a user identifier and attach your own file of up to 100 KB.
How are crashes symbolicated and deobfuscated?
On iOS and tvOS, crash-relevant frames are symbolicated on the device where symbol information is available, and you can upload dSYM files for full symbolication. On Android, upload your ProGuard or R8 mapping files to deobfuscate stack traces. Both can be uploaded from your CI through the REST API.
How does the AI crash analysis work?
Appelium Intelligence writes a concise summary for each crash group based on its latest crash report. The model runs on Appelium’s own infrastructure in Zürich, so your crash data is not sent to a third-party AI provider. For deeper root-cause analysis, connect your own AI agent, such as Claude, Copilot or Cursor, through the Appelium MCP server.
Can I get alerted when my app becomes unstable?
Yes. Set a crash-free sessions threshold, and Appelium alerts you when any of your applications drops below it. Alarms can notify your team in Slack, Microsoft Teams or Opsgenie and close automatically once the rate recovers.
What happens when a fixed crash comes back?
When you close a crash group, you can add the version that contains the fix. If the same crash is detected again in that version or a later one, the crash group reopens automatically.
Does Appelium also report non-fatal errors and ANRs?
Yes. With error reporting enabled you can report non-fatal errors with a single call, and Appelium automatically creates a report with a stack trace whenever the main thread is blocked for more than 5 seconds. Errors are grouped by message similarity.
Which plans include crash reporting?
Crash reporting and non-fatal error reporting are included in every plan, including the FREE plan for indie developers, for iOS, tvOS and Android apps.
Fix the crashes that matter, first
Symbolicated reports, the logs behind every crash and AI that helps you find the cause.
You are in a good company - Join over 150 apps!
Over 150 apps in Switzerland choose to use Appelium.
👨💻 Latest content from our Engineering blog:
XPCService
Strongly typed bidirectional communication channel between UIApplication and XCUIApplication with powerful APIs and super fast performance.
More about XPCService
Screen Flow Pattern in UI tests
Robust and scaleable pattern for structuring UI tests. Highly reusable screen verification code with human readable test case code. All flows and interactions statically typed 🙌.
More about the Screen Flow Pattern
SnapshotQuery™
Learn about SnapshotQuery - our latest addition to AppeliumTests which radically improves the performance of your XCUITests while making them more stable and reliable at the same time.
More about SnapshotQuery
Early access and news
Be the fist one to know about all the exciting engineering posts and product announcements.