Android App Keeps Crashing or Won’t Open? 10 Fixes That Preserve Your Data

Reviewed: September 22, 2026. When an Android app keeps crashing, freezes on launch or closes immediately, clearing everything is rarely the best first move. The safer approach is to work from low-risk checks toward destructive fixes, while figuring out whether the problem belongs to one app or the whole phone.

Google’s current Android troubleshooting guidance follows the same general pattern: restart and update first, then force stop, clear cache, and only later consider clearing app data or reinstalling. Menu names can differ between Pixel, Samsung, OnePlus, Xiaomi and other Android devices.

First: is it a crash, a freeze, or an “App isn’t responding” message?

These symptoms are related but not identical. A crash ends the app process or throws you back to the launcher. A freeze leaves the app visible but unable to react normally. Android’s Application Not Responding (ANR) condition is specifically triggered when the app’s UI thread is blocked long enough that Android considers it unresponsive. Google’s Android Developers documentation explains that a foreground input-dispatch ANR can occur when an app does not respond to an input event within the platform timeout; OEM behavior can vary.

That distinction matters for troubleshooting. Repeated ANRs in one app can point to work blocking that app’s main thread or an app-side defect; several unrelated apps freezing together makes device load, storage pressure or a broader system problem more plausible. A phone that actually reboots is a different symptom again — use our Android random restart and boot-loop guide instead of repeatedly resetting individual apps.

Second: is one app failing, or are many apps affected?

Open two or three unrelated apps that normally work. If only one app fails, focus on that app. If several apps are crashing, check storage, Android updates and recently installed or changed apps before erasing any app data.

If the failure started while Google Play was updating apps, first make sure the update actually completed. Our Google Play Store stuck-pending guide covers download and update failures separately; an incomplete update problem should not be treated as proof that the app’s local data is corrupt.

1. Restart the phone before changing app data

A restart clears temporary processes and gives Android and the app a clean launch state. After restarting, open the problem app before launching many other apps. If the failure disappears, there is no reason to clear storage or reinstall anything.

2. Update the app and Android

Open Google Play, go to Manage apps & device and install an available update for the affected app. Then check the phone’s system-update screen. Google specifically recommends checking both app and Android updates when an installed app crashes, will not open or stops responding.

An app can fail after either side of the compatibility boundary changes: a new app build can introduce a bug, while a major Android update can expose an incompatibility in an older app. If the crash started immediately after an update, check the developer’s support page or recent Play Store information before deleting local data.

3. Force stop the app, then reopen it

Go to Settings > Apps, select the affected app and use Force stop. The exact path varies by manufacturer. Force stopping ends the current app process without intentionally deleting its saved files, accounts or settings.

If the app launches normally afterward but repeatedly returns to the same failure, continue with the next checks rather than force stopping it every time.

4. Check free storage — especially when several apps are unstable

Low free space can contribute to broader Android instability and can prevent apps from creating temporary files, databases or downloaded resources. Google’s device-level crash guidance says phones can start having issues when less than 10% of storage is free. Treat that as a troubleshooting signal, not a magic threshold that proves storage is the cause.

Check Settings > Storage or your manufacturer’s equivalent. Do not respond by installing a random “RAM cleaner” or “phone booster.” Remove downloads you no longer need, uninstall genuinely unused apps, or move personal media to appropriate backup storage. Our Android storage-full guide explains a safer cleanup order.

5. Clear cache before clearing storage or data

For many apps, Android exposes Storage & cache > Clear cache. Cached files are intended to be temporary and can be rebuilt. Google describes cache clearing as a short-term troubleshooting step because cached data accumulates again over time.

Clear storage or Clear data is different. Google warns that data saved in the app can be erased. That can include offline downloads, local settings, databases or unsynced work, depending on how the app is designed. Use it only after you understand what is backed up.

6. Check permissions only when the crash follows a protected feature

If the app opens but fails when you use the camera, microphone, files, location or another protected feature, inspect its permissions under Android’s app settings. A denied permission does not guarantee a crash — well-designed apps should handle denial — but it can help isolate why one workflow fails.

Do not grant every permission as a blanket fix. Enable only access that makes sense for the feature you are trying to use. If the failure is specifically microphone-related, use our Android microphone troubleshooting guide.

7. Test connectivity if the app depends on the web

Google notes that web-based apps need a stable internet connection. If the app opens but hangs while loading an account, map, feed or cloud library, test another connection and another online app. A connectivity failure can look like an app failure.

If several online apps fail together, use our Android internet troubleshooting hub rather than clearing each app individually.

8. Reinstall only after protecting local data

If the app is still broken, uninstalling and reinstalling can replace damaged app files with a fresh copy. But uninstalling can erase locally stored app data. Confirm that important content is synced, exported or backed up before removing the app.

Google’s Android backup can include apps and app data, but Google explicitly notes that not every app can back up or restore all settings and data. If you are installing an APK rather than the Play Store build and Android reports an installation or update conflict, use our APK “App Not Installed” troubleshooting guide instead of repeatedly uninstalling a working signed build.

9. Use Safe Mode when multiple apps or the phone are unstable

Google’s Safe Mode guidance says downloaded apps are temporarily disabled, making Safe Mode useful when crashes, freezes or slowdowns affect the phone more broadly. The way you enter Safe Mode varies by manufacturer.

If the phone becomes stable in Safe Mode, remove recently downloaded or recently changed apps one at a time after returning to normal mode, restarting and retesting after each removal. Do not treat Safe Mode as proof that a particular app is guilty until the result is reproducible.

10. Contact the developer when the failure is app-specific

If one app still crashes after the phone and app are updated, a restart, force stop and cache clear — while other apps work normally — the developer is the right next escalation point. Include the phone model, Android version, app version, what action triggers the crash, whether you see an ANR message, and whether the failure started after an update.

That information is more useful than a generic “doesn’t work” report and avoids destructive troubleshooting that cannot fix a server-side or app-code defect.

When should you clear app data?

Clear data when the app is demonstrably stuck in a bad local state, you have protected anything important, and lower-risk steps have failed. It is reasonable for an app whose content is fully server-synced and easy to sign back into; it is much riskier for a recorder, notes app, downloader, authenticator, game or media tool with local-only content.

When is a factory reset justified?

Not for a single crashing app. A factory reset erases the phone and should be a last-resort device-level measure after backup, particularly when the operating system itself remains unstable and narrower troubleshooting has failed. If only one third-party app is broken, escalating directly to a factory reset is disproportionate.

Bottom line

For an Android app that keeps crashing or will not open, first identify whether you are seeing a true crash, an ANR/freeze or a phone-level reboot. Then determine whether one app or many are affected. Restart, update, force stop, check storage, clear cache, verify relevant permissions and connectivity, and protect local data before clearing storage or reinstalling. Use Safe Mode for broader instability and contact the developer when the evidence points to one app.

Sources: Google Android Help: Fix an installed Android app that isn’t working; Google Android Help: Fix an Android device that’s restarting or crashing; Google Android Help: Find problem apps by rebooting to Safe Mode; Android Developers: ANRs.