Android App Keeps Stopping: How to Fix It

When an app crashes, it is rarely your whole phone breaking. It is almost always one of a small handful of things: a corrupted cache, an outdated app, low storage, a permission the app needs but does not have, or the system killing the app to free up memory. There is also a sneakier cause where the app itself is fine but a shared component underneath it goes bad and takes several apps down at once. We will get to that one near the end because it explains the cases that make no sense otherwise.

The reason order matters is simple. Some fixes touch nothing personal. Others log you out and erase your settings. So you start light and only go heavier if the light fix does not hold.

A force stop ends every process the app is running and clears it out of active memory. That is more thorough than swiping the app off your recent-apps screen, which often leaves bits running. If the app got stuck in a bad state, this alone can fix it.

Open Settings > Apps, tap See all apps if you need to, pick the app, then tap Force stop and confirm. Open the app again and see if it holds. This loses nothing. No login, no settings, no files. It is the first thing to try every single time.

If the app crashes again right away, move on. Do not keep force-stopping in a loop and hoping. One try tells you what you need to know.

The cache is a pile of temporary files the app builds up so it can load faster. When one of those files goes corrupt, the app can choke on it and crash. Clearing the cache throws out those temporary files and nothing else. You stay logged in. Your settings stay. Your photos and downloads stay. The app just rebuilds the cache next time you use it, maybe loading a hair slower the first time.

Go to Settings > Apps > [the app] > Storage (it may read Storage & cache), then tap Clear cache. On Samsung phones the path is the same: Settings > Apps > [app] > Storage > Clear cache. Reopen the app.

This is the fix to reach for when an app is laggy, showing stale or wrong content, or crashing for no obvious reason. Because it costs you nothing, there is no reason to skip it. If clearing the cache fixes it, stop here. You are done.

Here is the one to be careful with. Clear data (sometimes labeled Clear storage) resets the app to how it was the day you installed it. You will be signed out. Your in-app settings, preferences, and any progress that is not backed up online will be gone. For a game with no cloud save, that can mean starting over. For a banking or messaging app, it means logging back in and setting it up again.

It does not touch photos, videos, or files saved to your phone's gallery or general storage. Those live separately. But anything the app kept inside itself is wiped.

So why do it at all? Because a deeply broken app state that survives a cache clear usually clears with a data wipe. Reach for this when the app keeps crashing after you cleared the cache, gets stuck in a sign-in loop, refuses to sync, or reopens broken after an update. Before you tap it, make sure you know your login details and that anything you care about is backed up. Path: Settings > Apps > [app] > Storage > Clear data.

A crash can simply be a bug that the developer already fixed. Open the Play Store, tap your profile icon, go to Manage apps & device, and check Updates available. Update the misbehaving app if there is one waiting. While you are there, it is worth updating Android System WebView and Google Chrome too, since a lot of apps lean on those to show web content inside themselves.

There is a second update most people never look at: the Google Play system update. This patches core components separately from your main Android version. Find it under Settings > Security & privacy > System & updates > Google Play system update. Menu wording shifts a little by brand, so if you cannot find it, search your Settings for "Play system update." Install anything pending and restart if asked.

Apps need free space to write temporary files, save state, and update themselves. When storage is almost full, apps start crashing in ways that look random. If you are sitting at a few hundred megabytes free, that is very likely your problem.

Check under Settings > Storage to see what is eating space. On Pixel phones you will find Free up space suggestions there. Clear out videos you have already backed up, offload large games you are not playing, and dump downloads you forgot about. As a rough guide, try to keep a couple of gigabytes free. Once you have breathing room, retry the app.

Some apps crash the moment they try to do something they are not allowed to do. A camera app with no camera permission, a maps app with no location, a messaging app with no storage access. The app asks, gets refused, and falls over instead of handling it gracefully.

Go to Settings > Apps > [the app] > Permissions and look at what is granted versus denied. Turn on the ones the app genuinely needs for what you are trying to do. Only grant what makes sense. A wallpaper app has no business reading your contacts, and you can leave that off without breaking anything.

If several unrelated apps start crashing in the same hour, your email, your bank, a shopping app, all closing within seconds of opening, the problem is almost certainly not those apps. It is a shared layer underneath them. Two usual suspects: Android System WebView, which apps use to show web pages inside themselves, and Google Play Services, which a huge number of apps rely on to run in the background. A bad update to either one can knock out many apps at the same time. This has happened before on a large scale, and Google has shipped fixes for it more than once.

First, open the Play Store and update Android System WebView and Google Chrome. A newer version often already contains the fix. If an update is not available yet, you can clear the cache for Google Play Services the safe way: Settings > Apps > See all apps > Google Play Services > Storage & cache > Clear cache. As a last resort while waiting for a fix, you can uninstall WebView updates from its Play Store page to roll back to an older, stable version, then let it update again later once the broken version is replaced. When one bad component is the cause, this is what gets your apps back, not poking at each app one by one.

If a single app still will not behave after everything above, uninstall it and install a fresh copy. This clears out a corrupted install and gives you the current version in one move. Touch and hold the app icon, tap Uninstall (or remove it from Settings > Apps), then reinstall from the Play Store.

Be aware this is effectively the same as clearing data: you will be logged out and local settings are gone, so have your account details ready. For most apps with cloud accounts, your real data comes back when you sign in. A quick restart of the phone before reinstalling is also worth a shot, since it clears out memory and stuck background processes that no single app setting will fix.