# A mobile app crash, caught with the file and line that caused it

> We asked for an order confirmation. The app crashed instead. The result names the error, the step it came after, the stack trace and the steps to reproduce it.

By Jason Nguyen, Founder, Testsy. Published 2026-11-20. https://testsy.dev/blog/catch-a-mobile-app-crash-with-its-stack-trace/

## A crash looks like nothing

When a website breaks, something stays on the screen: an error page, a spinner, a red message. When a mobile app crashes, it vanishes. The user is looking at their home screen.

That makes a crash oddly hard to report. A person testing by hand writes "the app closed when I placed the order". A test script reports that it could not find the confirmation text, which is true and useless. Neither tells the developer what they need: which error, in which file, after which tap.

The crash log has all of that. It is on the phone, and somebody has to go and get it.

## The test

This test does not mention crashes at all. It is an ordinary check of a checkout, written as plain text and run on an iPhone with iOS 27:

```text
Open Shop, tap Add Product A, then tap Place express order
and verify Order: confirmed #5001 · $10.00.
```

The app is QA Lab, our practice app. Its **Place express order** button has a bug planted in it: it crashes the app. The test was not told.

## What happened

![The moment before: one item in the cart, $10.00. The next tap is Place express order.](https://testsy.dev/blog/img/crash-frames.webp)

The tester added Product A, read "Cart: 1 items · Subtotal: $10.00", and tapped **Place express order**. The app disappeared.

The result came back 1 minute 23 seconds after the run started. It is the picture at the top of this page: "The app crashed", the error, the step it came after, the stack trace, the check that failed and the steps to reproduce.

Read it the way the developer who has to fix it would:

- **What**: `Fatal error: QA Lab: express checkout failed`, at `ShopCanvas.swift:254`. The file and the line.
- **Which kind**: `EXC_BREAKPOINT / SIGTRAP`, reported by the phone itself, not guessed from the screen.
- **When**: after step 6, "Tap: Place express order button".
- **Where in the code**: the stack trace, starting in the button's action inside `ShopView`.
- **How to see it again**: four steps to reproduce, ending "the app crashes instead".

The check that failed is stated as a check, too. Expected: "Order: confirmed #5001 · $10.00". Saw: the app crashed after express checkout and no confirmation was shown. The three checks before it passed and are listed as passed.

[Recording: The review video of the run, 13 seconds. The app closes right after the tap.](https://testsy.dev/blog/video/crash.mp4)

Open [the run](https://app.testsy.dev/share/cYGwPINCMlCECDmBnXWwp_6H2f4Li5EP) to see the whole trace. The link is read-only and stays live until 18 February 2027.

## Why this is the test to copy

Nobody wrote a crash test here. The crash was found by a test of something else, which is how crashes are found in real life.

So you do not need a list of crash tests. You need your ordinary journeys run on every build: sign in, search, add to cart, check out, change a setting. If any tap along the way takes the app down, the result says so in the terms above, and the run counts as failed rather than "could not find text".

Two things make the report more useful:

- **Send it to whoever fixes it.** A result has a [fix prompt](https://testsy.dev/docs/fix-prompt/) written for a coding agent. For a crash it includes the error, the step it came after and the top of the stack trace.
- **Run it where your users are.** Crashes are often tied to one OS version or to tablets. The same test runs on iOS 17 to 27 and Android 10 to 16, on phones and tablets, without rewriting it.

## Run it

Upload a build, choose **iPhone app** or **Android app** in **New test**, and describe one journey. [Proof, replay and video](https://testsy.dev/docs/results/) explains the crash card and the device log, and [Builds from CI](https://testsy.dev/docs/app-builds-ci/) shows how to run your tests on every build.

This post is one of a series: [The hardest parts of mobile app testing, each one run for real](https://testsy.dev/blog/the-hardest-parts-of-mobile-app-testing/).
