If an app just died and threw up “Unfortunately, [App] has stopped,” start with the three safest actions, in this order: force stop the app, restart the phone, then check the Play Store for an update to that app.
Those three fix a large share of crashes, and none of them touch your data.
If the crash survives all three, stop guessing and answer one question before you do anything else: is it one app, or several? That single answer decides everything that follows, because the same error message is used for completely different underlying failures.
This guide is organized around that question rather than around a generic list of fixes.
Find the pattern that matches what you’re seeing, work that path, and skip the rest.
What Android is actually telling you
This message is a death notice, not a diagnosis.
Android runs every app in its own process.
When that process ends unexpectedly — an unhandled error, a failed read, a resource the app expected and didn’t get — the system tears it down and tells you the app stopped.
Android knows the app died.
It does not know why, and the dialog is the same regardless of the reason.
That’s why “Unfortunately, App Has Stopped” has no single fix.
It’s one symptom with many possible causes, and the useful work is narrowing down which category you’re in.
The wording varies, and one variant means something different
Exact phrasing depends on your Android version, your manufacturer’s software, and sometimes the app itself:
- “Unfortunately, [App] has stopped.” — the classic phrasing used by older Android releases.
- “[App] keeps stopping.” — the wording newer releases typically use, often with buttons like Close app, App info, or Send feedback.
- “[App] has closed” or similar manufacturer-specific variants on some devices.
- “[App] isn’t responding.” — this one is different. The app hasn’t died — it’s alive but frozen, usually because it’s stuck doing work on the thread that’s supposed to be drawing the screen.
Android offers to wait or close it.
People describe all of this in different words — the app keeps crashing, the app stopped working, the app force closes, Android apps keep stopping.
With the exception of “isn’t responding,” they’re all describing the same underlying event: the app’s process ended and Android reported it.
The distinction matters.
A crash ends the process instantly and is often triggered by bad data, a missing permission, or a code fault at a specific moment.
A freeze usually points at something slow: a stalled network request, a huge file, a jammed database, or a device under heavy load.
If you’re consistently seeing “isn’t responding” rather than “has stopped,” give the app more time to finish, check your connection, and look at whether the phone is low on memory or storage before you start clearing things.
Start here: sixty seconds of triage
Match your situation to a row.
If more than one row fits, work the broader cause first — a system-level problem will keep breaking individual apps no matter how many times you reinstall them.
| What you’re seeing | What it usually points to | Go to |
|---|---|---|
| One app crashes; everything else is normal | A fault inside that app — its version, its stored data, its permissions, or its install | Path A |
| The app dies within a second or two of opening, every time | A fault on the startup path, and you can’t use the app to fix the app | Path B |
| Several unrelated apps are crashing | A shared layer underneath them: a system component, storage, or resources | Path C |
| It began right after an update of some kind | A compatibility change, a bad build, or app data the new version can’t read | Path D |
| The crashing app is preinstalled and can’t be uninstalled | A system app, which needs a different set of moves | Path E |
| The phone is nearly full, or crashes happen when saving or downloading | Storage exhaustion causing failed writes | Path F |
One more quick test that costs nothing and saves a lot of wasted effort: if the crashing app has a website, open it in your browser.
If the web version works fine, the problem is on your phone, not with the service.
Before you clear anything: what each step actually costs you
Most bad outcomes in Android troubleshooting come from people reaching for a destructive step too early.
Here’s what each action really does, ordered from harmless to irreversible.
| Action | What it does | Effect on your data | Reversible? |
|---|---|---|---|
| Restart the phone | Clears system memory and restarts every service; finishes any update waiting on a reboot | None | Yes |
| Force stop the app | Kills the app’s process and cancels its background work until you open it again | None, beyond unsaved work in that moment | Yes |
| Clear cache | Deletes temporary files the app can rebuild — thumbnails, prefetched pages, downloaded images | None.
Settings, logins and content stay. |
Yes (files regenerate) |
| Clear data / Clear storage | Resets the app to how it was the moment it was installed | Depends on the app.
Expect to be signed out and to lose settings and offline downloads. |
No |
| Uninstall updates (system apps only) | Reverts a preinstalled app to the version that shipped with the phone | May clear that app’s data; the app itself stays | Yes — Play can re-update it later |
| Uninstall | Removes the app and its private data together | Same loss as clearing data, plus the app is gone | Reinstallable, data usually not |
| Reinstall | Downloads a fresh copy of the current version with empty data | Starts clean; server-synced content returns after sign-in | — |
| Factory reset | Erases the entire phone and returns it to out-of-box condition | Everything on the device is deleted | No |
Cache and data are not the same thing
Cache is scratch space. It holds files the app downloaded or generated to make itself faster: image thumbnails, prefetched articles, map tiles, temporary copies.
Every one of them can be recreated.
Android itself deletes cached files automatically when the phone runs short on storage, which is exactly why clearing cache is safe — the system treats it as disposable, so the app must already be built to survive losing it.
Data is the app’s private storage: your sign-in token, your preferences, its databases, and anything you downloaded for offline use.
Clearing it doesn’t repair the app — it resets it to a brand-new install with the same version still in place.
Whether that hurts depends entirely on where the app keeps your things:
- Account-based apps that sync to a server — email, social, banking, streaming, cloud storage.
Clearing data typically signs you out and clears local settings, and your content comes back when you sign in again.
- Apps that store things only on the device — offline notes, some games and their saves, downloaded episodes and maps, scanners, trackers, authenticator apps.
Clearing data can permanently destroy content that exists nowhere else.
Authenticator apps deserve a specific warning: clearing their data can wipe the codes that let you sign in to other accounts.
Make sure you have recovery codes or a second enrolled device before you touch one.
Rule of thumb: before clearing data on any app, ask yourself one question — if this phone were lost tomorrow, would the contents of this app still exist somewhere? If yes, clearing data is a minor inconvenience.
If no, back it up first, or skip the step and escalate instead.
Where an app has its own delete-or-reset option inside its settings, Google’s guidance is to try that first.
Two practical footnotes.
Files an app wrote to shared storage — photos in your gallery, documents in Downloads, media on an SD card — usually survive clearing that app’s data, because they live outside the app’s private folder.
And clearing data doesn’t change the app’s version, so if the crash is caused by a bug in the current release, clearing data will not fix it.
Path A: one app is crashing and everything else is fine
When a single app fails while the rest of the phone behaves normally, the shared parts of Android are almost certainly working.
Stay focused on that app and escalate slowly.
1.
Force stop it, then open it again
Go to Settings > Apps > See all apps > [the app] > Force stop — the same action older versions of Android labeled “force close.” This ends the process outright, along with any background piece of it that’s stuck in a bad state.
Reopening starts it completely fresh.
Note that swiping the app away in the Recents view is not the same thing; force stopping is more thorough.
Why it works: crashes are often triggered by a process that got wedged and keeps re-entering the same failure.
Killing it clears that.
Risk: none.
If it fails: move on immediately — repeating it won’t help.
2.
Restart the phone
Not filler.
A restart clears system memory, restarts background services the app depends on, and completes any update that was staged and waiting for a reboot.
An app can crash because something outside it is unhealthy, and a restart is the cheapest way to rule that out.
3.
Update the app — and check whether it’s just you
Open the Play Store > profile icon > Manage apps & devices and update the app if an update is listed.
Crashes that affect many users are usually patched within days.
While you’re on the app’s Play Store page, do something most guides skip: read the newest reviews, sorted by most recent.
If dozens of people are reporting the same crash starting on the same date, the bug isn’t on your phone and nothing you clear will fix it.
The correct action is to wait for the update and report the crash — not to reinstall repeatedly or reset your device.
Also check whether you’re enrolled in that app’s test build.
In the Play Store > profile icon > Manage apps & devices > Beta, open the app and, under “You’re a beta tester,” choose Leave.
Beta versions are explicitly less stable, and leaving one means uninstalling it and reinstalling the public release — so expect to lose beta-side progress, and note that a spot in a full beta program isn’t guaranteed to be available again later.
4.
Check permissions — especially if you hadn’t opened the app in months
This is a genuinely common cause that rarely gets mentioned.
Android automatically resets the sensitive permissions of apps you haven’t used for a few months, and on newer versions it goes further: unused apps are hibernated, which force-stops them, clears their cache, and revokes their runtime permissions.
An app that suddenly crashes at launch after a long absence is often an app that lost a permission it assumes it still has.
Go to Settings > Apps > [the app] > Permissions and re-grant what it needs.
The control that governs this behavior sits on the same App info screen but is named differently depending on your version — roughly, “Pause app activity if unused” on newer releases, “Remove permissions and free up space” on the release before that, and “Remove permissions if app isn’t used” under Permissions on older ones.
5.
Check battery optimization (Samsung, Xiaomi, OnePlus, OPPO)
On these manufacturers’ phones, aggressive power management can kill an app’s process mid-task and produce exactly this crash — especially for apps that do work in the background.
Go to Settings > Apps > [the app] > Battery and set it to Unrestricted (wording varies: “Don’t optimize” / “No restrictions”).
Only do this for apps you trust — unrestricted apps use more battery.
6.
Clear the app’s cache
Settings > Apps > [the app] > Storage & cache > Clear cache. A single corrupt or half-written cached file that the app reads during startup will crash it every single time, and no amount of restarting will help.
This is the highest-value low-risk step in the entire guide.
If this fixes it: you’re done.
Don’t continue down the list, and don’t clear data “just to be thorough.” Use the app normally and see whether it recurs.
If it recurs within days: that’s a real bug in the app worth reporting, not a maintenance task you should have to repeat.
7.
If it’s a connected app, rule out the network and the clock
Apps that need a server can crash when the connection is unusable rather than merely slow.
Turn airplane mode off, switch between Wi-Fi and mobile data, and temporarily disable any VPN, ad-blocker, or custom Private DNS setting — those sit between the app and the internet and can break it in ways that look like an app fault.
Also check your date and time.
A wrong system clock breaks the secure connections apps rely on, and sign-in can fail hard enough to crash the app.
Google’s own troubleshooting includes deliberately re-syncing it: in Settings > System > Date & time, turn off automatic date and time zone, set the date and time to something wrong, then turn automatic settings back on.
8.
Clear the app’s data
Only now, and only after reading the risk section above.
Settings > Apps > [the app] > Storage & cache > Clear storage (labeled Clear data on some devices).
Why it works: the app’s saved state can become internally inconsistent — a corrupted database, a malformed setting, a stale session token — and the app crashes while reading it.
Resetting to a blank state removes the bad input entirely.
What to expect afterward: sign in again, redo your preferences, re-download anything offline, and re-grant permissions.
9.
Uninstall and reinstall
If clearing data didn’t do it, the app’s installed files may be damaged — an interrupted update, a partial download, a corrupted package.
Clearing data doesn’t touch those; reinstalling replaces them.
Long-press the app icon, choose to uninstall, then reinstall from the Play Store.
Be aware of the limitation: reinstalling gets you the same current version.
If the current version is the bug, reinstalling cannot fix it — and that is your signal to stop working this path.
10.
Reset app preferences — the gentlest system-level reset
If you’ve ever disabled apps, revoked permissions in bulk, or used a debloater tool, an app can crash because something it depends on was switched off.
Go to Settings > Apps > the ⋮ menu > Reset app preferences.
This re-enables disabled apps and restores default-app choices, notification settings, and background restrictions to defaults — without deleting any app data.
Risk: none to your files.
11.
One thing to check if you’ve ever used Developer options
If you turned on Developer options at some point, open them and confirm Don’t keep activities is off.
It destroys each screen the moment you leave it, and it surfaces crashes in apps that would otherwise run fine.
When to stop Path A: if force stop, restart, update, permissions, battery optimization, cache, network checks, data, reinstall, and reset app preferences have all failed, further repetition is wasted effort.
Either the app has a bug on your device configuration, or the cause isn’t inside the app at all — check whether anything else on the phone is misbehaving, then escalate.
One more possibility worth naming: if the app hasn’t been updated in a year or more, it may simply be abandoned — no fix on your phone will revive an app its developer stopped maintaining.
Find a current replacement instead.
Path B: the app crashes the instant it opens
This scenario is worth handling separately because it removes an option people don’t realize they’re relying on: you cannot get inside the app.
You can’t sign out cleanly, export your data, change a setting, or turn off the feature that’s breaking.
Everything has to be done from outside.
Work only with steps that don’t require the app to stay open:
- Force stop it from Settings, so nothing from the previous crash is still running.
- Restart the phone.
- Update it from the Play Store, which never requires opening the app.
- Clear its cache from Settings.
For instant-crash cases, a corrupt cached file read during startup is one of the most likely explanations.
- Check free storage (see Path F).
An app that can’t write during launch may die immediately.
- Check and re-grant permissions from Settings, especially if the app hasn’t been opened in months.
Before you clear data on an app you can’t open
This is the hard case, because the usual advice — export or sync your content first — assumes you can get into the app.
If the app has a website or a desktop version, sign in there and retrieve what you need.
If you have a second device with the same app and account, check whether your content is present there; if it is, the content is on a server and clearing data locally is low-risk.
If neither is true and the app holds something irreplaceable, treat clearing data as a genuine risk and contact the developer before you do it.
A few instant-crash causes specific to this pattern
- It started on a brand-new phone or right after a device-to-device transfer.
Restored app data can be incompatible with the freshly installed app.
Clearing data or reinstalling usually resolves it.
- The app was installed from outside the Play Store.
A build meant for another region, another chip, or a much older Android version may not run at all.
Some newer devices no longer include support for older 32-bit apps, so an aging sideloaded app can fail instantly with no route to fixing it other than a current version from the Play Store.
- The crash dialog offers “Send feedback.” Use it.
It attaches the technical crash details the developer actually needs, which no amount of describing the problem in a review can substitute for.
Path C: several unrelated apps are crashing
When apps that have nothing to do with each other start failing together, the common factor is underneath them.
Do not troubleshoot each app individually — you’ll clear caches all day while the real cause keeps knocking them over.
1.
Restart, then check storage
A restart matters more here than in Path A, because memory pressure and a wedged system service both produce exactly this multi-app pattern.
Then check free space, because a nearly full phone breaks many apps simultaneously (Path F).
2.
Check for a Google Play system update
Parts of Android are updated separately from the Android version itself.
Google ships core system components through the Play Store on their own schedule, which is why your phone has a Google Play system update level that’s distinct from its Android version.
The path varies: on many devices it’s under Settings > Security & privacy, and on Samsung devices it’s under Settings > About phone > Software information > Google Play system update.
Install anything pending and restart.
3.
Update Android System WebView and Chrome
Android System WebView is the component apps use to display web content inside themselves — a login screen, an in-app article, a help page, an embedded checkout.
A very large number of apps depend on it without ever telling you.
That’s what makes it capable of producing exactly this symptom: when WebView is broken, apps that seem unrelated all crash at once.
This isn’t hypothetical.
In March 2021, Google confirmed that a faulty WebView update was crashing apps on Android, including Gmail, and resolved it by shipping corrected WebView and Chrome builds through the Play Store.
Search the Play Store for Android System WebView and update it, then do the same for Chrome, which is tied to it.
In the rare case where the currently released WebView is the problem, you can temporarily revert it: Settings > Apps > See all apps > Android System WebView > menu > Uninstall updates.
Treat that as short-term only, and re-update once a fix ships — WebView carries security patches for every app that uses it.
Two cautions.
First, don’t do this for a single crashing app; if everything else works, WebView is almost certainly fine.
Second, don’t disable or remove system components as a general remedy — you’ll break things that were working.
4.
Update Google Play services, and treat its data as a last resort
Google Play services connects apps to Google features like sign-in, maps, and push notifications.
When it’s unhealthy, apps that depend on those features can fail.
You can’t uninstall it or force stop it, and it’s supported only on Android 7.0 and above.
Update it first, then, if needed, clear only its cache: Settings > Apps > Google Play services > Storage & cache > Clear cache.
Warning: clearing Google Play services storage is a genuine last resort.
Google’s own guidance says it may delete information saved to your device — including saved passwords and cards stored for payments and transit — and may require you to re-authenticate payment methods and sign in to your Google Account again on all your devices.
Exhaust everything else first.
Clearing the Play Store’s cache and data is a separate and much milder step, useful when the Play Store itself is misbehaving; it resets some Play Store preferences such as auto-update settings.
5.
Check whether you opted into a system services beta
It’s possible to enroll a device in Google’s public beta for system services, which is explicitly less stable and can cause apps to crash.
To leave it on the device: Settings > Google services and preferences > All services > System services > Leave beta.
After leaving, your device returns to the production version at the next release.
6.
Test in Safe Mode
If multiple apps are still crashing, find out whether something you installed is responsible.
See the Safe Mode section below — it’s the fastest way to split “an app I installed is interfering” from “the system itself is unhealthy,” and it determines whether you escalate to the app developer or to your manufacturer.
Path D: it started right after an update
Start with the honest caveat: timing is a strong hint, not proof.
Updates tend to arrive alongside other changes — a restore, a batch of newly installed apps, a phone that just crossed into being full — and any of those could be the real trigger.
Treat the update as your leading suspect, not your conclusion.
First, work out which update it actually was
Four different things get called “an update,” they ship on independent schedules, and they fail in different ways:
| Update type | Where to check it | How it typically breaks apps |
|---|---|---|
| App update | Play Store > Manage apps & devices | A bug in the new build, or new code misreading data written by the old build |
| Android version update | Settings > About phone > Android version | Platform behavior changes an older app wasn’t built for |
| Google Play system update | Settings > Security & privacy, or About phone > Software information | A shared component changed underneath apps that use it |
| Manufacturer software update | Settings > Software update, plus the build number in About phone | Vendor-specific changes, often around power management or customized system apps |
Then work the fix in this order
- Check for a newer app update. If a bad release is crashing users, a hotfix usually follows quickly.
This is the single most likely resolution for post-update crashes and it costs you nothing.
- Clear the app’s cache. Post-update crashes are frequently caused by leftover cached artifacts generated by the previous version.
The app moved forward; its scratch files didn’t.
- If it’s a preinstalled app, uninstall its updates to revert it to the factory version, then let Play update it again once a fix ships (Path E).
- Clear the app’s data if the app syncs to an account and step 2 didn’t help — old stored state that the new version can’t parse is a real and common failure.
- Reinstall if the update itself may have been applied incompletely.
- Report it. Post-update crashes are exactly the kind that developers fix fast when they get reports with version details.
Two things not to do
Don’t sideload an older APK of the app from a third-party site. You lose security patches, you can’t verify what you’re installing, downgrading can leave app data in a state the app can’t handle, and you’ll be stuck on a stale version that stops working when its servers move on.
Don’t count on rolling back Android. On retail devices, an Android version update generally can’t be undone by any supported route.
If a platform update genuinely broke an app, the fix comes from the app’s developer or a follow-up patch from your manufacturer — not from reversing the update.
Path E: the crashing app is one you can’t uninstall
Preinstalled apps — Phone, Messages, the camera, Settings, the Play Store, the Google app, your manufacturer’s own apps — can’t be removed.
They have a different toolkit, and one tool in it is unusually effective.
- Force stop, then clear the cache. Same as any other app.
- Uninstall updates. Long-press the app, open App info, then the overflow menu, then Uninstall updates.
This reverts it to the version that shipped with the phone.
For a system app that started crashing after an update, this is often the fastest fix, and it’s reversible — Play will bring the app forward again later, by which time the bug may be patched.
Note that it can clear that app’s data along the way.
- Clear data as the next step up, remembering that for the Play Store this resets Play preferences, and for Google Play services it carries the serious warning described in Path C.
- Disable it, if the app is one you don’t use and your device allows it.
Don’t disable anything you don’t recognize.
If Settings itself, your launcher, or the phone dialer is what keeps crashing, treat that as more serious than an app problem: restart, test in Safe Mode, install any pending system update, and if it persists, contact your manufacturer.
These are the components everything else depends on.
One easy thing to overlook: if your phone has multiple users, a guest session, or a work profile, make sure you’re signed in as the device owner.
Apps and permissions are managed per profile, and a work profile can be subject to policies set by your employer that you can’t change yourself.
Path F: storage and memory pressure
A nearly full phone is a common and badly underrated cause of app crashes.
Apps write constantly — session state, databases, logs, temporary files — and when a write fails because there’s no room, an app that doesn’t handle the failure gracefully simply dies.
At the same time, Android starts reclaiming space by deleting cached files, so apps lose files they expected to find.
The visible result is apps crashing for no obvious reason, often several of them.
Check Settings > Storage.
There’s no official threshold, but as a practical guideline, if you’re down to a couple of gigabytes or less, treat storage as your prime suspect before anything else.
Safe things to clear:
- Downloaded videos, podcasts and offline maps you’re finished with
- The Downloads folder
- Photos and videos already backed up to a cloud service — confirm the backup first
- Media accumulated by messaging apps, which is often the largest single item on a phone
- Apps you no longer use
What about RAM?
Memory is managed automatically, and closing everything in the Recents view is not a fix — Android will simply reload those apps, sometimes using more resources than if you’d left them alone.
On phones with limited RAM, heavy apps genuinely do get shut down to make room, but note the difference in symptom: a background app killed for memory usually just disappears quietly and restarts when you return to it.
It doesn’t normally produce a crash dialog.
If you’re seeing “has stopped,” memory management is rarely the whole story.
Safe Mode: a test, not a repair
Safe Mode starts your phone with only the software that came with it.
Apps you installed are temporarily disabled — not deleted, and nothing of yours is removed.
It exists to answer exactly one question: is something I installed causing this?
How to get in varies by manufacturer, and there is no universal button combination.
The most common method is to hold the power button to bring up the power menu, then press and hold Power off until a Safe Mode prompt appears.
On Pixel phones, if the phone is off, you can hold Volume down while it boots.
Other manufacturers differ — check your device maker’s own support page rather than guessing at key combinations.
Expect a couple of side effects: some home screen widgets are removed, and on Pixel devices airplane mode is turned on automatically, so you’ll want to turn it back off to test anything that needs a connection.
Then use the phone the way you normally would and read the result:
- The crashes stop in Safe Mode. Something you installed is involved.
Restart to exit, then uninstall recently added apps one at a time, restarting and testing between each, until the crashes stop.
The usual culprits are apps that hook into other apps by design: screen overlays and color filters, accessibility tools, VPNs, ad blockers, battery savers, and anything marketed as a cleaner or booster.
- The crashes continue in Safe Mode. A third-party app isn’t the cause.
Go back to Path C or Path D, and if those are exhausted, this is the evidence that justifies contacting your manufacturer.
You exit Safe Mode by restarting normally.
Nothing is repaired by staying in it.
Fix comparison: which fix, when
Every fix in this guide in one place — ordered from safest to most destructive, with the path that covers it.
| Fix | Data risk | When to use |
|---|---|---|
| Force stop + restart | None | First try for any crash (Path A) |
| Update the app | None | Crash started recently; others report it too (Paths A, D) |
| Clear cache | None | App dies at launch, every time (Paths A, B) |
| Check permissions | None | App unused for months (Paths A, B) |
| Reset app preferences | None | You disabled apps or used a debloater (Path A) |
| Battery: Unrestricted | None (uses more battery) | Samsung/Xiaomi/OnePlus, background kills (Path A) |
| Clear data | Signs you out; may lose offline content | Cache didn’t help; app syncs to an account (Paths A, B) |
| Reinstall | Same as clear data | Installed files may be damaged (Paths A, D) |
| Uninstall updates (system apps) | May clear that app’s data | Preinstalled app crashing after update (Path E) |
| Update WebView + Chrome | None | Several unrelated apps crashing (Path C) |
| Free up storage | None | Phone nearly full (Path F) |
| Safe Mode test | None | Suspect an installed app is interfering (Path C) |
| Factory reset | Erases everything | Last resort, verified backup only |
Prevent it from coming back
- Keep the app, Android System WebView/Chrome, and Android itself updated; leave app auto-update on.
- Keep at least a couple of GB of storage free.
- Install only from the Play Store — and skip cleaner/booster apps entirely.
- Don’t disable system components you don’t recognize.
- Leave beta programs unless you actually want to test.
- If an app misbehaves after months unused, check its permissions before anything destructive.
When to stop, and who to contact
Knowing when to stop is as valuable as knowing what to try.
Use this logic:
- One app crashes and everything else works → work that app’s update, permissions, cache, data, and install.
Don’t touch system components.
- The app crashes instantly → use only fixes that work from outside the app, and secure your data through the web or another device before clearing anything.
- Several unrelated apps crash → investigate the shared layer: storage, Google Play system updates, WebView, Play services, and Safe Mode.
Fixing them one by one is wasted effort.
- It began after an update → identify which update, look for a newer patch, clear the cache, and consider reverting a preinstalled app’s updates.
Don’t sideload old versions.
- Clearing cache fixed it → stop and monitor.
- Clearing data fixed it → restore what was reset and watch for recurrence.
- Reinstalling didn’t help → stop reinstalling.
The cause is either a bug in the current version or something outside the app.
- Nothing helped → escalate, using the evidence you’ve gathered.
Reading the result: what the fix tells you
- Clearing the cache fixed it. Stop here.
Don’t continue down the list “to be safe.” Just watch it — if the crash returns within a week or two, that’s a bug in the app worth reporting rather than a chore you should keep repeating.
- Clearing data fixed it. The app’s saved state was the problem.
Sign back in, redo your preferences, re-download offline content, and re-grant permissions when the app asks.
If it crashes again after a few days of normal use, the app is corrupting its own data — report that, and mention it recurs after a reset.
- Reinstalling fixed it. The installed files were damaged.
If it comes back, the install wasn’t really the cause; return to the diagnostic table.
- An update fixed it. Leave automatic updates on.
This is the outcome you want.
- Safe Mode identified an app. Don’t reinstall it from an unofficial source hoping for a better copy.
Report the conflict to its developer and use an alternative in the meantime.
Contact the app’s developer when
The problem is confined to one app, other apps work, and a fresh install still crashes.
You’ll get a far better response if you include: the app version, your Android version, your exact device model and build number, precisely what you do before it crashes, whether it happens on a clean reinstall, and what you’ve already tried.
If the crash dialog offers Send feedback, use that too — it attaches technical details you can’t reproduce by hand.
Developer contact details are listed on the app’s Play Store page.
Contact your device manufacturer when
Multiple unrelated apps crash, the problem survives Safe Mode, preinstalled system apps are failing, or it started immediately after their software update.
Manufacturers customize Android heavily, and behavior specific to One UI, HyperOS, OxygenOS or another vendor layer can only be fixed by the vendor.
If your phone is under warranty and the fault looks hardware-adjacent — crashes tied to the camera, storage, or mobile network — get it looked at rather than resetting it.
Contact Google Play support when
The Play Store itself won’t work, you can’t update any apps at all, or the problem clearly sits with Google Play services after you’ve tried the safe steps.
About factory reset
A factory reset erases everything on the phone.
It’s a legitimate step, but only under narrow conditions: many apps crashing, the problem surviving Safe Mode, every relevant step above exhausted, and a verified backup in hand.
It is the wrong tool in most situations people reach for it, for a specific reason: a factory reset doesn’t change app versions.
If a buggy release of an app is the cause, you’ll wipe your phone, reinstall the same app, and get the same crash — which is precisely what manufacturers caution about.
It also can’t fix a problem that’s on the developer’s servers, and it can’t undo a system update.
And if the crash survives a factory reset, the cause was never your software setup to begin with — suspect a hardware fault such as failing storage or memory, and contact your manufacturer instead of resetting again.
Back up first, and only reset when the evidence actually points at your device’s own software being broken.
Mistakes that make this worse
| Mistake | Why it hurts |
|---|---|
| “Just factory reset it — that fixes everything.” | It erases your phone and leaves a buggy app version exactly as buggy.
Almost always the wrong first move. |
| “A cleaner or booster app will repair it.” | Nothing in a third-party app can repair another app’s internals.
These frequently add overlays and background services that cause more crashes than they resolve. |
| “I’ll grab a working APK from a download site.” | Unverifiable builds, no security updates, possible data corruption from downgrading — and a genuine malware risk. |
| “Clearing app data is harmless.” | For account-based apps it’s a minor reset.
For apps holding local-only content it can be permanent loss. Check before you tap. |
| “Clear Google Play services first, it fixes app problems.” | It’s a last resort that can remove saved passwords and payment cards and force you to sign in again across devices. |
| “It must be a virus.” | The overwhelming majority of these crashes are ordinary software faults.
Malware is possible, but assuming it leads people to install exactly the kind of app that causes real harm. |
| “The Android update definitely broke it.” | Likely suspect, not proof.
Confirm which update actually happened before acting on that theory. |
| “Closing all apps in Recents keeps things stable.” | Android manages memory on its own.
Constantly force-closing apps doesn’t prevent crashes and can make performance worse. |
| “I’ll just reinstall it a few more times.” | Reinstalling gives you the same version.
If it failed once, repeating it changes nothing — change your diagnosis instead. |
| “These steps are the same on every Android phone.” | Menu names, Safe Mode entry, and update paths differ by manufacturer and Android version.
Steps that don’t match your screen aren’t steps you should force. |
Quick answers
Will I lose my photos, messages, or account?
Restarting, force stopping, and clearing cache don’t remove anything.
Clearing an app’s data or uninstalling it removes that app’s private data — which for account-based apps means signing in again, and for apps that only store things locally can mean real loss.
Photos and files saved to your gallery or Downloads live outside an individual app’s private storage and typically aren’t affected.
A factory reset erases everything.
Is clearing the cache safe?
Yes.
Cached files are temporary and rebuildable, and Android deletes them on its own when storage runs low.
The only effect you’ll notice is the app loading a little slower the next time while it rebuilds them.
What’s the difference between “has stopped” and “isn’t responding”?
“Has stopped” means the app’s process ended unexpectedly — it crashed.
“Isn’t responding” means the app is still running but is frozen, usually stuck on slow work.
They’re different failures and often have different causes.
Why does one app crash while everything else works fine?
Each Android app runs in its own isolated process with its own storage and permissions.
A fault in one app’s code, saved data, or install is contained to that app.
That isolation is the whole reason a single crashing app tells you to leave the rest of the system alone.
Can an Android update really cause apps to stop working?
Yes.
Platform updates change behavior, and an app built against older expectations can break.
Post-update crashes are also caused by app data written by an older version, partially applied updates, and shared system components changing beneath the app.
The usual resolution is an app update from the developer, not reversing the system update.
Do I need an antivirus app to fix this?
No.
This error is almost always an ordinary software fault.
Installing security or cleaner apps in response is more likely to introduce new problems than to solve this one.
Can I go back to an older version of an app?
Not through the Play Store, and downloading an old APK from a third-party site isn’t a safe substitute.
The one legitimate version rollback is leaving a beta program: leave the beta in the Play Store, then uninstall and reinstall the public release.
It crashes on my phone but works on my friend’s — what does that mean?
That it depends on something specific to your device: your Android version, your manufacturer’s software, your storage situation, your permissions, or your copy of the app’s data.
It also rules out a widespread outage, which means the fixes in Path A are the right place to spend your time.
How do I know whether it’s my phone or the app’s servers?
Open the same service in a mobile browser.
If the website works while the app crashes, the problem is on your device.
If the service is down everywhere and other users are reporting the same crash in recent Play Store reviews, waiting is the correct response.
Will “Reset app preferences” delete my data?
No.
It re-enables disabled apps and resets default-app, notification, and background-restriction settings.
Your apps, accounts, and files are untouched — it’s one of the safest system-level steps.
Can a bad SD card cause “app has stopped”?
Yes, if the app reads from it.
Remove the SD card and open the app again — if the crash stops, the card is corrupt.
Back up what you can and replace it.
The app crashes only on Wi-Fi (or only on mobile data) — why?
A network-level blocker is the usual cause: a VPN, ad-blocker, or custom Private DNS setting.
Disable them one at a time and retest.
What actually causes the “Unfortunately, app has stopped” error?
Always the same event: the app’s process ended unexpectedly — an unhandled error, a failed read, or a resource the app expected and didn’t get.
The trigger varies: corrupt cached or stored data, a missing permission, a bug in the current version, a damaged install, a conflicting app, or a shared system component failing underneath it.
That’s why the dialog never names a cause — Android only knows the app died, not why.
Why does “Unfortunately, [App] has stopped” appear even when I’m not using the app?
Apps run background pieces — sync services, push handlers, scheduled jobs — that can crash without the app ever opening on screen.
Treat it like a normal crash of that app: force stop it, clear its cache, check for an update, and look at battery-optimization settings, which can strangle background work on Samsung, Xiaomi, OnePlus, and OPPO phones.
If it’s a preinstalled app, uninstalling its updates often resolves it.
Can I recover data from an app after clearing its data?
Usually not from the phone itself — clearing data is the point of no return for anything stored only on the device.
If the app syncs to an account, sign back in and your content returns from the server.
Some apps keep a web dashboard or recycle bin worth checking.
This is why the guide insists on the one-question test before clearing data: if this phone were lost tomorrow, would the app’s contents still exist somewhere?
Is it safe to use third-party “system repair” software to fix crashes?
Be skeptical.
No PC program or app can fix a bug in another app’s code — what these tools actually do is reinstall firmware or wipe the phone, which is a factory reset with extra steps and a price tag.
They also ask for deep access to your device.
The manual steps in this guide do everything such software can legitimately do, without handing your phone to a stranger.
Thanks for reading! How to Fix "Unfortunately, App Has Stopped" on Android you can check out on google.