mobile app crashing on launch: support triage steps

TL;DR

Crash-on-launch is either a bad build, a corrupt local state, or a device the app no longer supports. Get the app version and OS version before anything else, because that pair answers half these tickets instantly. Reinstall is the fix people reach for, but it wipes local data, so it goes last, not first.

The query

mobile app crashing on launch: support triage steps

Use this when

• The app closes the moment it opens
• Crash reports spike after a new release
• Only some devices or OS versions are affected
• You need the mobile-crash macro
• A user says "it worked yesterday"

Not for

• Crashes in the middle of using the app
• Login errors inside a working app
• The backend being down
• Slow performance that is not a crash

Steps

1. Get the app version, OS, and device model

Ask all three in one message so you are not playing twenty questions. "Which version of the app, which phone, which OS version" is the whole triage in one line. Compare against your known-good and known-bad lists.

Expected output: the version triple, matched against your release notes.

2. Check whether it is a bad release

Look at your crash reporting and recent tickets. If crashes cluster on one app version, it is the build, not the user. Tell the user a fix is coming and give them the workaround or the rollback path instead of debugging their phone.

Expected output: a build-level cause confirmed or ruled out.

3. Force-stop and relaunch before anything drastic

On iOS, swipe the app away from the app switcher. On Android, force stop it from the app info screen. Then relaunch. This clears the corrupted in-memory state that causes a surprising share of launch crashes, with zero data loss.

Expected output: the app opens, or the crash survives a clean launch.

4. Clear the app cache or offload, not a full delete

On Android, clear cache from app info. On iOS, offload the app, which keeps documents while refreshing the binary. Both fix corrupt local data without the nuclear option.

Expected output: the app launches with user data intact.

5. Reinstall only as the last resort, with a data warning

If nothing else works, delete and reinstall, but first confirm their data is synced or backed up. Say explicitly what will be lost: downloaded files, offline content, unsynced drafts. Then collect the crash logs if your platform provides them.

Expected output: a fresh install, or logs in hand for engineering.

Ready-to-use message

Let's sort this out. Can you tell me:

1. The app version (find it in the app store listing)
2. Your phone model and OS version

First try: swipe the app fully closed and reopen it. If it
still crashes, go to the app's info screen and clear the cache
(Android) or offload the app (iPhone), which keeps your files.

Don't delete and reinstall yet. That wipes anything not synced,
so it's our last step, not our first.

Variant phrasings

app crashes immediately when I open it

Steps 1 and 3. Version triple first, then the force-stop relaunch.

app keeps crashing after update

Step 2 first. Post-update crash waves are the build until proven otherwise.

how to fix app crash on startup for users

Steps 3 through 5 in order. Escalate the order: relaunch, cache, reinstall.

Why it happens

Launch is the moment the app reads all its saved state at once: settings, cached files, auth tokens, databases. If any of that state got corrupted, or if a new build misreads old state, the app dies before it can even show an error screen. That is why these crashes feel so total and why the gentler fixes work: you are giving the app clean state to wake up to.

Edge cases

• Crash only on very old OS versions: check your minimum supported version. The honest answer may be "your OS is no longer supported," with an upgrade path.
• Beta OS users: their crashes are expected and should go to the beta channel, not the main queue. Tag them separately.
• Crash after a phone restore or transfer: state corruption from the migration. Reinstall is actually the right first move here.
• Enterprise-managed devices: MDM profiles can block the app from launching. Ask if the phone is company-managed before deeper debugging.
• User already reinstalled and lost offline files. Acknowledge it, check what the server can restore, and note the loss in the ticket so the team sees the cost of the nuclear option.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstyZzGO0H7yVxrcm-gXsiDw