Fix "Unfortunately, App Has Stopped" Error on Android

The Error

You tap an app and get a dialog:

Unfortunately, "App" has stopped.

The app closes immediately. Reopening it triggers the same dialog — or it crashes after a few seconds. This isn't an app stuck in a restart loop. It means the app hit an unrecoverable exception: corrupted cache, a revoked permission, or broken internal data.

Why This Happens

The moment an app process terminates with an unhandled exception, Android kills it and shows this dialog. No retry, no graceful exit. The most common causes:

Corrupted cache — stale or malformed cached data causes the app to crash on load
Corrupted app data — databases, SharedPreferences, or internal files are in a broken state
Missing runtime permissions — Android 6.0+ requires explicit user grants; a revoked permission crashes any app that doesn't handle the denial gracefully
Incompatible update — a recent app or OS update broke something in the app's internals
Insufficient storage — the app can't write temporary files and bails immediately

Step-by-Step Fix

Step 1: Clear App Cache

Start here. It's completely safe — this removes only temporary files, not your personal data.

Go to Settings → Apps → [App name] → Storage → Clear Cache

Reopen the app. Loads normally? The crash was a bad cache entry. Done.

Step 2: Clear App Data

Cache didn't fix it? Go deeper. Clearing app data resets it to a fresh-install state. You'll lose locally stored settings, login sessions, and offline data — but anything synced to a server stays safe.

Settings → Apps → [App name] → Storage → Clear Data

Reopen the app and run through its initial setup.

Step 3: Check and Re-grant Permissions

A missing permission is a silent killer. Head to:

Settings → Apps → [App name] → Permissions

Look for anything set to Denied or Ask every time and switch it to Allow. The usual suspects: Storage, Contacts, Phone, Camera.

Step 4: Check Available Storage

A packed device is a common culprit. Apps crash the moment they can't write temp files.

Settings → Storage — aim for at least 500 MB free for normal operation

Delete unused apps, clear other app caches, or offload media to an SD card or cloud storage.

Step 5: Uninstall and Reinstall

Still crashing? The APK itself might be corrupted — something a data reset can't fix. A clean reinstall often solves it.

Long-press the app icon → Uninstall
Reinstall from Google Play Store

Don't restore from a backup right away. Let the fresh install run first and confirm the crash is gone before bringing your data back.

Step 6: Diagnose with ADB Logcat (Developer Fix)

For developers — or stubborn crashes that survive every step above — ADB logcat reveals the exact exception and line number causing the problem.

Connect your device via USB with USB Debugging enabled, then run:

adb logcat -c
adb logcat *:E | grep -i "your.package.name"

Reproduce the crash. The output names the exact exception. Common patterns:

# NullPointerException — uninitialized object
FATAL EXCEPTION: main
java.lang.NullPointerException: Attempt to invoke virtual method on a null object reference

# Permission denied at OS level
java.lang.SecurityException: Permission Denial: reading com.android.providers.contacts

# Database corruption
android.database.sqlite.SQLiteDatabaseCorruptException: database disk image is malformed

To filter only fatal crashes:

adb logcat AndroidRuntime:E *:S

On rooted devices, pull the app's data directory to inspect corrupted files directly:

adb shell run-as your.package.name ls /data/data/your.package.name/

Step 7: Roll Back to a Previous Version

Crash started right after an update? Roll back:

Settings → Apps → [App name] → ⋮ (menu) → Uninstall Updates (system apps only)
Third-party apps: download the previous APK from a trusted source and sideload with adb install -r app-old.apk

Verify the Fix

Open the app — it should launch without the crash dialog
Navigate to the screen that was crashing before
Trigger the action that caused the crash (loading a specific item, tapping a button, etc.)
Run adb logcat AndroidRuntime:E *:S in parallel to confirm no new exceptions appear

Tips

Skip the task killers — they don't prevent crashes and can trigger them by cutting off writes mid-operation
Check for Play Store updates — open Play Store → Library → see if the app has a pending update
Try Safe Mode to rule out third-party interference: hold Power → long-press Power off → tap Safe Mode. If the app runs fine there, another installed app is the culprit
Factory reset is the absolute last resort — back up everything first: adb backup -apk -shared -all -f backup.ab