Android Apps Crashing? Find the Right Fix in 30 Seconds

Every crash-fix page opens with the same advice: clear the cache. The advice is right when the app truly crashed, and useless when Android quietly ended the app to reclaim memory.

The 30-second test: did the app crash, or did Android kill it?

A crash and a memory kill produce the same symptom, but they behave differently while you watch. Google documents the crash side precisely: Android terminates the app's process and displays a dialog to let the user know that the app has stopped. A memory kill never shows a dialog, because the system is reclaiming memory, not reporting a fault.

What you saw	What happened	The branch that fixes it
A dialog said the app keeps stopping	The app crashed	The cache rail
No dialog; the app closed silently and restarts cold	Android killed it for memory	The memory branch
Many apps began failing on one day	A shared component, usually Android System WebView	The WebView fix
Only the heaviest apps die, camera first	Real memory pressure	The memory branch

If your problem is not on the table above, the pillar's one-line triage for sixteen problems covers the other common faults.

The app crashed: clear the cache the right way

Google's app-fix help orders the ladder the same way every time: restart the phone, update the app and Android, force stop, then clear cache and data. Each rung is cheaper than the one after it, so start at the top.

1. Restart the phone.
2. Update the app from the Play Store's Manage apps & device screen.
3. Force stop, then clear cache. Google's path is Settings > Apps > [app] > Storage & cache > Clear cache. On HiOS, the Settings search bar finds the App info screen fastest.
4. Clear storage only if the crashes continue. Google's storage help defines the pair: clearing cache removes temporary files, while clearing storage removes all app data.
5. Uninstall and reinstall when every rung above fails. Anything saved inside the app is deleted with the uninstall.

Google honestly marks the cache clear as a short-term solution: a cache clear buys stability back without repairing the app's code. Samsung walks Galaxy owners through the same restart, update and cache ladder before reaching a factory reset. A TECNO or Infinix owner meets the same ladder under HiOS or XOS names.

Many apps at once: the WebView fix

When every app fails on the same day, your apps are innocent. Apps that show web pages borrow one shared component, Android System WebView, so a fault there reads as everything breaking at once. Samsung's incident page for the March 2021 outage records a WebView fault crashing many apps at once, fixed by updating WebView and Chrome.

1. Open the Play Store, tap your profile picture, then Manage apps & device.
2. Update Android System WebView and Google Chrome.
3. If the Update button is missing for WebView, tap Enable first, then update; that path comes from Samsung's incident note.

Then check what else updated on the day the crashes started; the Play Store's manage view sorts by recently updated. If the whole phone feels slow since the update rather than apps dying, that is a different condition, and our slow-after-update guide covers it.

You will also meet rollback advice: install an older version from an APK site. An APK install skips every check Google applies to Play Store apps, and on a phone carrying bank apps and mobile money the trade is poor.

No dialog, the app just vanished: the memory kill

Google separates the two words plainly: storage keeps your files, memory runs your programs. A kill happens in memory, because Android treats free memory as wasted memory. The system fills RAM on purpose, and when the pressure is real, it kills the least essential processes: background apps first, system processes last.

The "free memory is wasted" premise flips the usual advice. A full RAM bar is Android working normally. A cleaner app selling you "freed" memory is undoing the system's own filing. Four things change a kill pattern, and none of them is a cache clear:

1. Keep storage with room to spare. A full phone cannot install its own fixes. Our storage cleanup guide clears a phone that never empties.
2. Restrict the apps you never open. Background apps die first in the kill order. The battery draining guide shows which apps are worth restricting.
3. Uninstall the RAM cleaner and the booster, which force-stop everything Android had filed away, so the next app you open starts cold and costs more than the cleaner freed.
4. Stop swiping every app out of Recents. A swipe is a force stop. A cold restart is the most expensive open an app can make.

One pattern names the memory branch: the heaviest apps die first. A Moto G owner on Reddit reported two years of the same crashes: "Very low usage apps are safe, but the second you try and use something more intense like camera or internet browser, it seems to fail to have memory". The documented kill order runs background apps first, so a camera dying while you hold it points at extreme memory pressure or a deeper fault. No written description can separate extreme memory pressure from a deeper fault.

Safe mode: what it proves, and what it cannot

Safe mode restarts the phone with every downloaded app silenced. Google's logic is clean: if the problem goes away in safe mode, a downloaded app is likely causing it, and if it stays, an app is not the cause. Google delegates the entry steps to each manufacturer, so follow your maker's instructions, never a universal button combo from a forum.

A crash that continues in safe mode clears every downloaded-app suspect, and the case moves to the memory branch or a deeper fault.

The record Android keeps, and why you cannot read it

Android does know whether the app crashed or the system killed it for memory. The system records why each app died: a crash, low memory, or a user force stop, which includes swiping the app away from Recents. The record is written for developers and their tools; no screen in Settings shows it to a phone owner. The dialog test is the only check an owner can actually run.

The Tecno Spark 40 on the bench

The phone behind this guide is a Tecno Spark 40 running HiOS on Android 15. The full bench method lives in our how to test an Android phone guide.

When the problem is not a crash at all

• A phone running hot protects itself and misbehaves while doing it; the overheating guide separates that case.
• Apps that check the clock misbehave when the time is wrong, which is why Google's app-fix help keeps a change-then-revert date and time trick.
• A battery that sags under load shuts the phone down; shutdowns are a different fault from a crash.

A note on the 73 percent statistic

One claim you will meet on repair-chain blogs says over 73 percent of smartphone users in Kenya experience app crashes weekly. A quoted-phrase search for the sentence finds no source behind it, only pages repeating it, so this guide quotes no crash figure. Ask of every number: whose count, and who counted?

Questions readers ask

How do I tell a crash from a memory kill?

A crash shows the "keeps stopping" dialog; a kill is silent and the app restarts cold.

Does clearing cache delete my photos or chats?

Clearing cache removes temporary files only. Clearing storage removes all app data: logins, settings and any chats the app keeps on the phone; gallery photos survive both.

Do RAM cleaner and booster apps stop crashes?

No. Cleaners and boosters force-stop apps Android was managing, so everything you open next starts cold and costs more memory, not less.

Why do apps crash right after a system update?

A new Android often brings a new WebView; update WebView and Chrome before blaming the update.

Should I install an older version of the app?

Installing an older version takes an APK from outside the Play Store, which skips Google's checks. On a phone with bank apps and mobile money, the rails above are the safer route.

What to do next

Run the thirty-second test once, and the page collapses to the branch that is yours. If the test sends you to the cache ladder, the work is ten minutes and Settings-deep.