An app keeps crashing on Android: the triage that fixes most of it

An app that crashes is asking for triage in the right order, because the heavy-handed fixes (reinstall, clear data) destroy state you may want — logins, offline work, settings. Five minutes of pattern recognition first: crashes on open points at the app's saved state or its update; crashes on one specific action points at that feature (a camera permission, a corrupt file it reads); started after an app or system update points at a version conflict. The ladder below goes lightest-touch first.

The fix ladder

1. Close it properly and retry once. Swipe it out of recents and reopen — a single crash is a data point, a pattern is a bug, and arestart clears the corrupted-memory case. 2. Check storage. Crashes-on-open are disproportionately a full-disk symptom — Android apps need working space, and near-full phones break apps in ways that look random: the storage-full mechanism and the cleanup that fixes it. 3. Update the app. The store listing's "update" button fixes the single most common crash class: a bug the developer already fixed. Same for Play system / OS updates when they're pending. 4. Clear the app's cache. Settings, then Apps, then the app, then Storage, then Clear cache: wipes junk the app wrote, keeps your logins and settings. Safe, fast, fixes the corrupt-saved-file family. 5. Clear storage (the honest reset). Same screen, Clear data: the app returns to first-run state — fix for the corrupted-preferences case, at the cost of signing in again. Do this before reinstalling; it fixes most of the same bugs without re-downloading anything. 6. Reinstall. Only now: uninstall and install fresh. Same cost as step 5 plus a download; do it when the store update itself was the suspect (an interrupted update corrupts installs).

The permission-shaped crash

A crash triggered by one action — sending a photo, recording audio — is often the app mishandling a denied permission: it asked for the camera, Android said no (permanently, possibly years ago), and a well-built app asks again while a buggy one dies. Check what the app is allowed to do and grant the relevant one; if the crash follows the permission like a shadow, the developer owns the bug.

When it's the developer's problem

Worked the ladder, still crashes on a clean install with full storage and current OS? That's a bug in the app, full stop — and it's worth ten seconds to report (store listing, scroll to the developer contact; Play Store reviews with "crashes on [device], after [action]" genuinely get read). Meanwhile: your data was never only in that app, was it? Backups are how app tragedies stop being data tragedies — the 3-2-1 habit applies to phones exactly as to everything else. And the battery-heat cousins of this story live in battery health, honestly.