Android 'Unfortunately, [App] Has Stopped' – 3 Fixes That Work

Cause 1: Corrupted Cache Files

Think of cache as the phone's short-term memory for each app. It stores bits of data so the app loads faster next time. Over time, that cache gets corrupted — maybe from a bad update, a partial download, or just a random glitch. When the app tries to read that junk data, it crashes.

I've seen this happen most often after a system update on Samsung Galaxy phones and Pixels. You launch Instagram, Gmail, or even the camera app, and bam — “Unfortunately, [App] has stopped.”

Here's the fix. It clears out the junk without deleting your personal data like photos, messages, or passwords.

1. Open Settings on your phone.
2. Scroll down and tap Apps (on stock Android) or Applications (on Samsung).
3. Tap See all apps if you don't see the crashing app right away.
4. Find the app that's crashing and tap on it.
5. Tap Storage & cache (on Samsung it might say Storage).
6. Tap Clear cache. Don't tap “Clear storage” or “Clear data” yet — that wipes your login info and settings.

After you clear the cache, go back and open the app. It should start up fresh. If it still crashes, move to the next cause.

Cause 2: A Buggy App Update

Developers roll out updates, but sometimes those updates break things. A recent update on your phone could have introduced a memory leak or a compatibility issue with your Android version. This is especially common with big apps like WhatsApp, Facebook, or banking apps right after they push a new version.

The fastest fix is to roll back the app to its previous version. That's called uninstalling updates, and it works on most pre-installed apps (like Chrome, Maps, or Gmail). For apps you downloaded from the Play Store, you can also try uninstalling and reinstalling — but that wipes your data. So let's try the less destructive route first.

For pre-installed apps (system apps)

1. Go to Settings > Apps and tap the problematic app.
2. Tap Uninstall updates (usually at the bottom).
3. Confirm when asked.
4. You'll see a message: “This app will be replaced with the factory version.” That's fine.
5. Open the app. It'll be like a fresh install, but without your custom settings.

If the app works after that, you can reinstall the update from the Play Store — but maybe wait a week until the developer fixes the bug. You can also turn off auto-updates for that specific app if you want. In the Play Store, open the app's page, tap the three-dot menu, and uncheck “Enable auto-update.”

For downloaded apps (from Play Store)

If the app isn't a system app, you can't “uninstall updates.” Instead, do this:

1. Go to Settings > Apps and tap the app.
2. Tap Force stop.
3. Tap Storage, then Clear data (this resets the app to default, so you'll lose settings and logins).
4. Go back and tap Uninstall.
5. Go to the Play Store, search for the app, and reinstall it.

After reinstalling, sign in again and test. This usually fixes crashes caused by a corrupt update or bad local data.

Cause 3: Outdated Android System WebView

Android System WebView is a hidden component that lets apps display web content. When it gets outdated or corrupted, tons of apps that rely on embedded browsers — like Gmail, Twitter, or LinkedIn — will crash on launch.

This was a huge issue in 2021 when a WebView update bricked many apps. It still happens today, mostly on older devices or after a failed system update.

Here's how to update it:

1. Open the Play Store.
2. Search for Android System WebView.
3. If it says Update, tap it.
4. If it says Open, it's already up to date.

If that doesn't help, try this:

1. Go to Settings > Apps.
2. Tap Android System WebView.
3. Tap Disable (you'll get a warning, but it's okay).
4. Now tap Enable again.
5. Restart your phone.

That forces the system to re-register WebView. After the restart, test the app that was crashing.

One more thing — if you're on Android 13 or 14 and using Chrome, WebView might be handled by Chrome itself. In that case, update Chrome from the Play Store and try again.

Quick reference: which fix to use when

I've done this drill hundreds of times. Start with cache — it's the least destructive and fixes most cases. If that fails, look at updates. And if you're dealing with multiple apps crashing, you're almost certainly in WebView territory.

One last tip: after any of these fixes, give the app a minute to settle. Sometimes the first launch after a clear can be slow because it's rebuilding the cache. Don't panic if it takes a few extra seconds to open.