Quick Answer
Android apps usually crash because of software bugs, outdated components (the app, Android System WebView, Google Play services, or the OS), low memory or storage, corrupted app data, or aggressive battery/background limits. Quick fixes include updating the app and WebView/Chrome, clearing cache or storage, freeing space, disabling battery optimizations for the affected app, and restarting the phone. If the issue started after an update, reinstall the app or roll back WebView/Chrome updates. Persistent crashes often point to device-specific bugs or incompatible sideloaded builds.
What Counts as a Crash?
A crash is when an app closes itself with a “keeps stopping” message or drops back to the home screen. You might also see an ANR (App Not Responding) warning, where the app freezes and Android offers to close it. Both indicate an unhandled error, a resource shortage, or that the app was blocked or killed by system restrictions.
Common Reasons Android Apps Crash
Outdated app or Android version
Apps built for newer APIs can misbehave on older Android releases, and older builds can fail on current versions due to changed permissions, background rules, or libraries. If you’re several versions behind on either the app or the OS, compatibility bugs are more likely.
Android System WebView or Chrome issues
Many apps render web content through Android System WebView (or Chrome as the WebView provider). A buggy or outdated WebView can crash mail clients, banking apps, and social apps. More than once, widespread outages were traced to bad WebView updates that required an urgent patch.
Low memory or aggressive background limits
When RAM is tight, Android kills background processes. If an app depends on a service that gets reclaimed, it can crash or hang when you return to it. Developer options like “Don’t keep activities,” third‑party task killers, and some OEM “RAM boosters” make this worse.
Corrupted cache or app data
Damaged temporary files, failed database migrations, or partial updates can trigger instant crashes on launch or after login. Clearing cache—and, if needed, app storage—often resolves these problems.
Storage nearly full or bad SD card
Apps need space for cache, logs, and updates. When internal storage falls below a few hundred megabytes, writes can fail and apps crash. Apps installed on, or writing to, a failing or slow SD card also crash frequently.
Conflicting updates or unstable beta builds
Joining a beta (for the app, WebView, Chrome, or the OS) can introduce breaking changes. Staged rollouts sometimes conflict with older components on your device until every dependency catches up.
Battery optimizers and background restrictions
OEM battery managers (MIUI, EMUI, ColorOS, One UI, etc.) and Android’s own optimizations can kill background services, breaking notifications, VoIP calls, and media playback. Some apps must be whitelisted to run reliably in the background.
Network problems and timeouts
Poor connectivity, captive portals, strict firewalls, VPNs, private DNS, or ad blockers can cause repeated failures that look like crashes, especially in apps that don’t handle network exceptions well.
Permissions denied or revoked
From Android 11 onward, permissions can auto‑reset for unused apps. If an app expects camera, storage, or location access and gets denied, it may crash instead of handling the error gracefully.
Device-specific bugs and driver issues
GPU/codec driver quirks, older OpenGL/Vulkan implementations, or OEM customizations can crash games, camera apps, and video players on certain models or chipsets.
Sideloaded or incompatible builds
Installing an APK meant for a different CPU architecture (arm64 vs armv7 vs x86) or Android version can cause instant crashes. Mismatched split APKs are a frequent culprit when sideloading.
Quick Fixes You Can Try Now
- Force stop and relaunch the app: Settings > Apps > [App] > Force stop, then open it again.
- Update the app: Play Store > profile > Manage apps & device > Updates available > Update.
- Update Android System WebView and Chrome: In Play Store, search “Android System WebView” and “Google Chrome” and update both. On some devices, Chrome is the WebView provider.
- Clear cache, then storage if needed: Settings > Apps > [App] > Storage & cache > Clear cache. If crashes persist, tap Clear storage (this resets the app and may sign you out).
- Restart your phone: A fresh boot frees memory and restarts services cleanly.
- Free up internal storage: Keep at least 1–2 GB free. Remove large downloads, move media to cloud or SD (if reliable), and clear other apps’ caches.
- Disable battery optimization for the app: Settings > Apps > [App] > Battery > Unrestricted (wording varies). Also check Settings > Apps > Special app access > Battery optimization.
- Check permissions: Settings > Apps > [App] > Permissions > Allow needed items (Camera, Files and media, Location, Microphone, etc.).
- Switch networks and disable VPN/ad blockers: Try mobile data vs Wi‑Fi, turn off VPN, private DNS, or ad‑blocking apps to rule out filtering.
- Reinstall the app: Uninstall, reboot, then reinstall from the Play Store. Avoid restoring the app from an old backup if crashes began after an update.
Targeted Fixes by Symptom
| Symptom | Likely Cause | What to Try |
|---|---|---|
| Crashes right after the splash screen | Corrupted data, incompatible build, missing permission | Clear storage, reinstall from Play Store, grant permissions on first launch |
| Apps with web content all crashing | Broken/outdated WebView or Chrome | Update WebView and Chrome; if it started today, uninstall WebView updates and reboot, then update again |
| Only on a specific Wi‑Fi or when VPN is on | DNS/firewall blocking, captive portal, TLS inspection | Disable VPN, try mobile data, set Private DNS to Automatic/Off, forget and rejoin the network |
| Works after force stop, then crashes later | Battery optimization killing background services | Set app battery to Unrestricted; optionally lock the app in Recents if your OEM supports it |
| Game crashes during graphics‑intensive scenes | GPU driver issues, thermal throttling, low RAM | Lower graphics settings, close other apps, keep the device cool, update OS and GPU drivers if your OEM provides them |
| Camera or video apps crash when recording | Permission mismatch, codec/encoder bug, low storage | Grant Camera/Microphone/Storage permissions, free space, use lower resolution/bitrate, update the app |
| Crashes started after a system update | App not yet updated for the new Android version | Update the app, opt out of betas, contact the developer with logs; check for a pending system patch |
| Only sideloaded app crashes | ABI mismatch or split APK parts missing | Install the correct architecture build for your CPU or use a trusted store that delivers complete packages |
When System Apps Crash (Gboard, Play Services, etc.)
If core services crash, many apps will misbehave. Try these steps in order:
- Update Google Play services and Play Store: Play Store > profile > Settings > About > Update Play Store. For Play services, search “Google Play services” in Play Store and update if available.
- Update or reinstall WebView/Chrome: Update both in the Play Store. If the crash began recently, go to Settings > Apps > Android System WebView > three‑dot menu > Uninstall updates, reboot, then update again.
- Clear cache for system components: Settings > Apps > Google Play services > Storage & cache > Clear cache; repeat for the Play Store and WebView/Chrome.
- Switch default keyboard temporarily: Settings > System > Languages & input > On‑screen keyboard > Manage keyboards > enable another keyboard, then update Gboard.
- Check for a system update: Settings > System > Software update. OEMs often push hotfixes for widespread crashes.
Advanced Troubleshooting
Boot into Safe Mode
Safe mode disables third‑party apps. Long‑press the power button > touch and hold “Power off” > tap OK to reboot in Safe Mode (steps vary). Test the crashing app. If it works here, a recently installed app, overlay, or optimizer is the cause. Uninstall suspicious tools like task killers, cleaners, screen recorders, floating widgets, or bubble/overlay apps.
Check overlays and accessibility services
Apps that draw over others or use accessibility can conflict. Go to Settings > Apps > Special app access > Display over other apps and temporarily disable for chat heads, filters, or floating toolboxes. Then check Settings > Accessibility and turn off nonessential services to test.
Reset app preferences
This restores disabled apps, default handlers, and background restrictions without deleting user data. Go to Settings > Apps > three‑dot menu > Reset app preferences. Reopen the crashing app.
Review Developer Options
If you’ve enabled Developer options, ensure “Don’t keep activities” is off and “Background process limit” is Standard. Resetting these avoids forced app restarts that look like crashes.
Leave betas and reinstall stable builds
In the Play Store, open the app page, scroll to “You’re a beta tester,” and leave the beta. Uninstall the app, reboot, and install the stable version. Do the same for Chrome and Android System WebView if you joined their betas.
Report the crash with useful details
Open the app’s Help & feedback or Send feedback. Include your device model, Android version, app version, steps to reproduce, and screenshots. On Pixel and some OEMs, you can share a bug report from Settings > About phone > Send feedback.
How to Prevent Future Crashes
- Keep apps, WebView/Chrome, and core services updated automatically via the Play Store.
- Maintain at least 10% free internal storage to keep caching and updates smooth.
- Avoid third‑party task killers and aggressive “RAM boosters.” Android manages memory on its own.
- Install apps from trusted sources only to avoid incompatible or tampered builds.
- Review permissions on first launch and allow what the app reasonably needs to function.
- Restart your phone periodically to clear transient glitches in services.
Frequently Asked Questions
Why do my apps crash only on Wi‑Fi or only on mobile data?
Network‑specific filtering is usually to blame. Captive portals, strict firewalls, DNS over HTTPS, VPNs, private DNS, or ad blockers can interrupt connections and trigger unhandled errors. Test on the other network, disable VPN/private DNS, and forget/rejoin the Wi‑Fi. If the issue disappears, adjust router, DNS, or VPN settings.
Is clearing cache or storage safe? What’s the difference?
Clearing cache deletes temporary files and is safe; you won’t lose personal data. Clearing storage (or “Clear data”) resets the app to first install, removing settings, offline files, and logins. Try cache first; use storage only if crashes persist.
Should I use a RAM booster or task killer to stop crashes?
No. Task killers often make crashes worse by terminating background services and forcing cold starts. Android already reclaims memory intelligently. Focus on freeing storage, disabling battery optimizers for affected apps, and keeping apps updated.
How do I roll back an app or WebView update that caused crashes?
For regular apps: Play Store > app page > Uninstall > then install again (if the previous version is still offered). For Android System WebView or Chrome: Settings > Apps > [component] > three‑dot menu > Uninstall updates, reboot, then update again when a fixed build is released. Avoid sideloading random APKs unless you fully trust the source and architecture.
Why do games crash more than other apps?
Games push GPU/CPU limits, allocate large memory blocks, and rely on drivers and codecs that vary by device. Heat, low RAM, outdated graphics drivers, and high settings can all trigger crashes. Lower graphics options, close background apps, keep the device cool, and install system updates.
When should I factory reset my phone to stop crashes?
Only after you’ve tried updates; cleared cache/storage; reinstalled; tested in safe mode; and reset app preferences. If multiple unrelated apps crash across profiles and even in safe mode, a reset can clear deep configuration or migration issues. Back up your data first, and test the problematic app before restoring all other apps.