“App keeps stopping”: the six causes worth checking
The message is the same whatever went wrong, which is why the usual advice is a list of things to try at random. Timing narrows it down fast: an app that dies within a second of launching has a different class of problem from one that runs for minutes and then falls over.
Start with when it crashes
| When it dies | Most likely cause |
|---|---|
| Instantly, every time | Incomplete install, missing split, or wrong architecture |
| After the splash screen | Corrupt app data, or a failed migration after an update |
| Only on one screen | A genuine bug in that feature, often with a specific file or account |
| After several minutes | Memory pressure, the system killing it under load |
| Only on mobile data | A network or region check failing |
| Since the last system update | Compatibility with the new Android version |
Werbung
The fixes, cheapest first
- Force stop, then reopen Clears a wedged process. Takes five seconds and occasionally is the whole answer.
- Clear the cache, not the data Fixes crashes caused by a corrupt cached file without signing you out.
- Restart the phone Genuinely useful when several apps misbehave at once, which points at a system service rather than any one app.
- Clear the app data Resets the app to a fresh state. You will lose local settings and sign-ins, so check for a cloud backup first.
- Reinstall from a complete package Fixes a partial install, and fixes the wrong-architecture case as long as you take the variant matched to your phone.
- Roll back one version If the crashes started with an update, the previous build is the fastest working answer while the developer fixes it.
When the phone, not the app, is the problem
Android kills background apps under memory pressure, and on a phone with 3 GB or less this happens constantly. It looks exactly like a crash: you switch away for a minute, come back, and the app restarts from its first screen.
The signs are that it affects several apps, gets worse when the browser has many tabs open, and improves right after a restart. The fix is to reduce what is running rather than to reinstall anything.
- Uninstalling apps you no longer use
- Using the Lite build of a heavy social app
- Keeping fewer browser tabs open
- Freeing storage below the ten percent mark
- RAM cleaner and booster apps
- Killing apps from the recents screen
- Clearing cache on a schedule
When it is the developer's problem
If a fresh install of the current version crashes on a supported Android version, you have found a bug, and no amount of clearing will fix it. Note your phone model, Android version and the app version, and send that. It is more useful than the crash description and it is what the developer will ask for first.
Note when it crashes, then work down from force stop to clear cache to reinstall to rolling back. Skip the cleaners entirely.
Frequently asked questions
Does clearing data delete my account?
Not the account itself, but it signs you out and removes anything the app stored only on the device, including offline downloads.
Should I use safe mode?
It is a good test when several apps misbehave. If everything is stable in safe mode, a third-party app, often one with accessibility or overlay permission, is interfering.
Can a failing SD card cause this?
Yes, and it is easy to miss. If apps that read media crash and others do not, take the card out and test.
Read next
This is not a rivalry. Each does something the other cannot.
You are not buying encryption. You are buying an operator whose income does not depend on you.
For a plain ZIP either works. For a split, password-protected archive, only one does.
