Android 'Unfortunately, [App] Has Stopped' Fix
Your Android app keeps crashing with 'Unfortunately, [App] Has Stopped'. Here's how to fix it step by step, from the most common cause to the sneaky ones.
1. Corrupted App Cache or Data (Most Common)
This is the fix that works nine times out of ten. An app's cache gets bloated or corrupted over time—especially after an Android update or a bad app update. You don't need to reinstall anything yet.
What to do:
- Open Settings on your phone.
- Tap Apps (or App Manager on Samsung phones).
- Find the app that's crashing—let's say it's Instagram.
- Tap Storage & cache (on older Android, it's just Storage).
- Tap Clear cache. You'll see a small confirmation—just tap OK.
- Do not tap Clear data yet. That will log you out and reset the app. Only do that if clearing cache doesn't work.
After clearing cache: Open the app again. It should load without the error. If it still crashes, go back and tap Clear data (this will erase your login and settings, but it's a clean slate). Then reopen the app and sign in again.
Real-world trigger: I see this most often after a Google Play System Update or a major OS update like Android 13 to 14. The app's cached files don't match the new system libraries.
2. Outdated App or System WebView
If clearing the cache didn't work, the problem is likely a version mismatch. Many Android apps rely on Android System WebView—a hidden component that lets apps show web content.
What to do:
- Open the Google Play Store.
- Tap your profile icon in the top-right corner (your face or initial).
- Tap Manage apps & device.
- Tap the Updates available tab. You'll see a list of apps needing updates.
- Find the crashing app and tap Update next to it. If you see Android System WebView in that list, update it too—that's often the real culprit.
- After updating, restart your phone. I know it sounds old-school, but it forces the new version to load properly.
After the update: Open the app. If it still crashes, go back to the Play Store and check for any pending updates for Google Play Services or Google Chrome—both can cause the same error.
Real-world trigger: I've seen this happen when someone disables automatic updates and then an app gets a critical update three months later while the WebView stays on an old version. The crash is almost instant.
3. Third-Party App Interference or System Glitch
If you're still stuck, something else is messing with the app. This could be a battery saver, a VPN, or a corrupted system process.
What to do: Boot into Safe Mode
- Press and hold the Power button on your phone until the power menu appears.
- Press and hold the Power off option on the screen. You'll see a prompt asking to reboot into Safe Mode.
- Tap OK (or Safe Mode). Your phone will restart with the words "Safe Mode" in the bottom-left corner.
- Now open the crashing app. If it works fine in Safe Mode, you know a third-party app is the problem. Common offenders: battery optimizers, launcher apps, or any app that claims to "boost" performance.
- To leave Safe Mode, just restart your phone normally.
If the app works in Safe Mode: Uninstall any recently installed apps, especially ones that modify system behavior (like Nova Launcher or Greenify). Reboot normally and test the crashing app again.
Real-world trigger: I had a user whose banking app crashed every time she opened it. Turned out her "battery saver" app was killing the banking app's background process. Uninstalled that battery app, problem gone.
Quick-Reference Summary Table
| Cause | Fix | Effectiveness |
|---|---|---|
| Corrupted cache/data | Clear cache first, then clear data if needed | Works about 90% of the time |
| Outdated app or WebView | Update the app, Android System WebView, and Play Services | Works for another 5% of cases |
| Third-party app interference | Boot into Safe Mode; uninstall conflicting apps | Covers the remaining 5% |
One more thing: If none of these fix it, consider doing a factory reset—but only as a last resort. Back up your photos and contacts first. I've seen people skip that step and lose everything. Don't be that person.
Was this solution helpful?