Android 'Unfortunately, [App] has stopped' – 3 fixes that work

1. Clear the app cache and data (solves 80% of cases)

The culprit here is almost always a corrupted cache file. Android stores temporary data for every app, and when that data gets stale or gets corrupted after an update, the app chokes. I've seen this on Samsung Galaxy S21s, Pixel 6s, and even cheap Motorola phones.

Here's the fix, exactly as I'd walk a junior tech through it on a call:

1. Open Settings → Apps → find the crashing app (e.g., 'Messages' or 'Google Play Services').
2. Tap Storage & cache → Clear cache. Don't touch 'Clear data' yet.
   If the app still crashes, go back and tap Clear storage (this wipes login data and settings, but it's often necessary).
3. Reboot the phone. Yes, a full power cycle flushes leftover crap.

Don't bother with 'Force stop' at this stage — that's a temporary bandage. Clearing storage is the real fix for most apps. The only exception is system apps like com.android.phone — don't clear data on those unless you're willing to re-pair Bluetooth devices and re-enter APN settings.

I ran into this on a user's Galaxy A52 last week — 'Photos' kept crashing after a July security patch. Cleared cache, still crashed. Cleared storage, fixed instantly. The user lost nothing because Google Photos syncs to the cloud.

2. Force stop and update the app (works when cache isn't enough)

If clearing cache didn't work, the app itself is likely buggy. This happens a lot with apps that haven't been updated for the current Android version. The Google Play Store rolls out updates gradually, so you might be sitting on a version that has a known crash on Android 14.

Steps:

1. Go to Settings → Apps → tap the crashing app → Force stop.
2. Open Play Store → tap your profile icon → Manage apps & device → Updates available.
3. Find the crashing app and tap Update. If no update shows, check the app's Play Store page — sometimes the developer pulled the latest update because of a bug, and you need to wait.

A specific scenario I've seen multiple times: Google Play Services crashes on older Android 12 builds. The fix isn't cache — it's updating Google Play Services via the Play Store. If the Play Store itself is crashing, sideload the APK from APKMirror (only if you're comfortable with that).

Power tip: If you're on a Samsung device and One UI Home keeps crashing, it's almost always a corrupted update. Force stop it, then go to the Galaxy Store and install any system updates. I've seen this on One UI 5.1 and 6.0.

3. Boot into Safe Mode to find a bad third-party app (rare, but nasty)

When a single app crashes system-wide — like 'System UI has stopped' — that's often caused by a dodgy third-party app that injects overlays or alters system behavior. Things like custom launchers, icon packs, or even a flashlight app with an overlay permission.

Safe Mode disables all third-party apps. If the error stops, you know one of them is the problem.

1. Press and hold the Power button until the power menu appears.
2. Long-press Power off until you see 'Safe Mode' prompt. Tap Enter Safe Mode.
3. Use the phone normally for 10 minutes. If no crash, restart normally (not in Safe Mode) and start uninstalling recently installed apps one by one.
4. The usual suspects: custom launchers (Nova, Lawnchair), wallpaper apps, or any app that uses Draw over other apps permission.

I've seen this exact issue on a Pixel 7 where a 'battery saver' app was causing System UI to crash every 5 minutes. Safe mode confirmed it, uninstalling the battery app fixed it. Don't waste time reinstalling the OS — it's almost never Android itself.

Quick-reference summary

Try these in order. You'll fix 95% of 'unfortunately has stopped' errors without factory resetting or flashing anything. Save the big guns for when nothing else works.