You tap the icon, watch the splash screen flash for a half-second, and boom — you're back on the home screen. Or the app just refuses to open, sometimes with a “keeps stopping” message, sometimes with nothing at all. I've seen this on every Android device from a budget Moto G to a Galaxy S24 Ultra. The root cause varies, but the fix path is almost always the same. Skip the wild goose chase and work through these in order. You should be done in under ten minutes unless something's really bent.
Fix 1: Clear the App's Cache (30 seconds)
This is the “did you turn it off and on again” of app crashes, and it works more often than you'd think. The cache can get corrupted after an update or when the storage fills up. Clearing it forces the app to rebuild its temporary files, which usually kills the “app closes instantly” symptom.
- Open Settings → Apps (or Application Manager on some phones).
- Find the app that's crashing. If you don't see it in the list, tap See all apps.
- Tap Storage → Clear Cache. Don't hit Clear Data yet — that wipes your login and settings, which is a last resort.
- Relaunch the app.
If it opens, you're done. If it still closes, move on.
Fix 2: Update or Reinstall the App (5 minutes)
A stale version is another common culprit. Developers push updates that fix crash bugs, especially after a major Android OS release. If you haven't updated the app in a while, that's your problem. Also check if the app itself has a pending update in the Play Store — sometimes the Play Store auto-update is off and you're running a version that's two months old.
Go to the Play Store, search for the app, and tap Update. If there's no update available, uninstall it and reinstall. That does a clean sweep — removes all corrupted local data and pulls the latest APK. You'll lose any settings stored locally, but for a crashing app, you've got nothing to lose.
Wait — try Safe Mode first if the app started crashing right after you installed something else. Reboot into Safe Mode (hold the power button, then long-press Power off until the Safe Mode prompt appears). If the app works in Safe Mode, a bad third-party app is screwing with it. Uninstall your most recently installed apps and reboot normally.
Fix 3: Pull the Crash Log with Logcat (15+ minutes)
If the app still crashes, you're dealing with something deeper — a native crash, a missing system resource, or a conflict with the OS. This is where guessing stops and debugging starts. You'll need a computer with ADB (Android Debug Bridge) installed. If you don't have it, grab Platform Tools from the Android developer site and install it — it's just a zip file you unzip and run from the command line.
Here's the drill:
- Enable Developer options on your phone. Go to Settings → About phone → tap Build number seven times.
- In Developer options, turn on USB debugging.
- Plug the phone into your computer and run:
adb logcat -c
then clear logcat before launching the app:
then launch the app manually, and when it crashes, run:
adb logcat -d | grep -i "FATAL EXCEPTION" | head -50
The output will show you the exact error. Look for lines like java.lang.NullPointerException or Unable to start activity — that tells you the exact component that's failing. You can then search that error message online, but honestly, if you're at this point, the fix usually means clearing data (not just cache) or, if it's a pre-installed system app, resetting app preferences.
Note: For system apps (like the dialer or camera), you can also try Settings → Apps → tap the three-dot menu → Reset app preferences. It doesn't delete data, just resets disabled apps and permissions — sometimes that's all it takes.
One more thing: check your storage. If you're under 500MB free, Android's low-memory killer can close apps at random. Free up space and see if the crash frequency drops. That's not a fix, just a workaround, but it'll keep you going until you can clean house.
That's it. Start with the cache, move to updates/reinstall, then get serious with logcat. Most people never get past step one. You'll be the exception.