Most app crashes on a phone or computer come from one of three repeatable causes: a full storage drive, a corrupted app cache or update, or a background process starved of memory. Work through the fixes in order of likelihood rather than rebooting at random — the steps below move from a two-minute check to a fifteen-minute reinstall, and the first two resolve the majority of cases on both Android and iOS.

The order matters because the cheap checks rule out the expensive ones. If your phone has 400 MB free, no amount of clearing cache will stop the next crash. If a single app dies while everything else runs fine, you have an app problem, not a device problem — and the diagnostic in section two tells you which within about thirty seconds. Nothing here requires a factory reset until you have exhausted the step-by-step ladder, and the reset appears near the end for a reason.

Check Free Storage Before Anything Else

Open Settings, then Storage, and read the number at the top. Android flags a low-storage warning below roughly 10 percent of total capacity; iOS shows a similar alert and starts offloading apps when space runs short. Treat 1 GB of free space as the working floor on any phone, and 10 percent of total capacity as the safer target on a 128 GB device.

Why the number matters: every app needs scratch space to write temporary files while it runs. When the drive is full, those writes fail and the app exits — often silently, with no error message. A crash that happens only after twenty minutes of use, or only when you open the camera inside another app, is a classic storage symptom.

Do the cleanup in this order. Delete downloaded video and offline music first, because they consume the most space per tap. Then clear the cache inside your three heaviest apps (Settings, Apps, pick the app, Storage, Clear cache on Android; offload and reinstall on iOS). Empty the trash or recycle bin in Photos — on both platforms deleted photos linger for 30 days and still count against storage until purged.

On a computer the same rule holds with different numbers. Windows needs roughly 10–15 percent of the system drive free for the page file and temp writes; below that, applications fail in ways that look like random crashes. Check with File Explorer, right-click the C: drive, Properties. If you are under the threshold, move large files off first — a crash caused by storage will not respond to reinstalling the app.

Tell Apart an App Crash From a System Crash

Count what fails. One app closing repeatedly while the rest of the phone behaves is an app-level fault. Two or more unrelated apps closing, plus a reboot or a frozen home screen, points at the system or the hardware. That split decides whether you spend the next ten minutes in the app's settings or the device's.

Look at the crash pattern, too. A crash on launch within two seconds usually means a corrupted install or an incompatible update. A crash after several minutes of use suggests memory pressure or overheating. A crash tied to one action — sending a photo, switching to the rear camera, opening a map — narrows it to a permission or a specific hardware handoff.

On Android you can read the actual record. Open Settings, then About phone, then look for Build number; tap it seven times to unlock Developer options, then go to System, Developer options, Bug report and take an interactive report. The log names the failing package. On iOS there is no user-facing log, but Settings, Privacy & Security, Analytics & Improvements, Analytics Data lists crash entries named after the app and date.

If the crashes began within a day or two of a system update, note that timing before you change anything else. Updates reset permissions and can leave old app data in a format the new OS no longer reads. That pattern is fixable with the reinstall in section six, and it is worth knowing before you start clearing things you did not need to clear.

Force-Stop and Clear Cache, Then Clear Data Only If Needed

Force-stop ends every process the app owns and clears its in-memory state. On Android: Settings, Apps, select the app, Force stop. On iOS the equivalent is swiping the app card up out of the app switcher — Apple's own support pages describe closing an app this way, and it does not delete anything. Reopen the app and watch whether the crash repeats.

If it does, clear the cache next. Android: Settings, Apps, select the app, Storage, Clear cache. This deletes temporary files only and never touches your account, saves, or messages. iOS has no per-app cache button, so the closest equivalent is offloading the app: Settings, General, iPhone Storage, select the app, Offload App. Offloading removes the app binary but keeps its documents and data, and reinstalling restores it.

Clearing data is the bigger hammer, and most guides skip the cost. Android's Clear data wipes the app back to a fresh install — logins, local saves, downloaded content, and any drafts stored on the device. Before you tap it, check whether the app syncs to an account; if it does, your data returns on sign-in. If it does not, you lose it. That distinction is the difference between a five-minute fix and a lost afternoon.

Sequence the three actions deliberately. Force-stop first because it is instant and reversible. Cache second because it is safe on every app. Data third, and only after you have confirmed the app stores nothing locally that matters. If the crash survives a data clear, the problem is in the app version or the system, not in your files.

Update or Roll Back the App and the Operating System

Check the app version before you update it. On Android, Settings, Apps, select the app, App info shows the version number at the bottom. On iOS, the App Store listing shows version history under the app name. Write the number down — if a fresh update caused the crash, that number is what you are rolling back from.

Update both the app and the system, in that order. An app built for a newer OS version can misbehave on an older one, and the reverse happens just as often after a major OS release. Android: Settings, System, System update. iOS: Settings, General, Software Update. Then update the app itself from Google Play or the App Store, and check for pending updates across all installed apps while you are there.

Rolling back is harder than updating, and the honest answer differs by platform. Android allows sideloading an older APK from a source you trust, but that bypasses Play Protect scanning and is not something to do casually. iOS does not permit downgrading an app at all; the App Store serves only the current version. If a specific update broke the app on iOS, your realistic options are waiting for the developer's fix or using the web version.

Watch for the update that fixes the crash you already have. Developers ship crash fixes constantly and rarely announce them, so the version notes are worth a glance. A crash that has persisted for a week on an app you use daily is often one update away from disappearing — and reinstalling from the store in section six pulls the current version automatically.

Close the Memory and Background-App Pressure

Memory pressure is the crash cause people misdiagnose most often, because the symptom looks random. When free RAM runs low, the system kills background apps to protect the foreground one — and sometimes kills the foreground one anyway. On Android, Settings, Developer options shows Running services and the memory figures behind it; on iOS there is no user-facing RAM readout, so you infer from behavior instead.

The behavior signature is specific. Apps crash after you have used a dozen others, or after a long session with the camera or a game. The app that dies is not the one you were using heavily. If that pattern fits, close the apps you are not using — on Android from the recents button, on iOS by swiping cards up — before opening the one that keeps failing.

Restart the device as a real fix, not a ritual. A reboot clears leaked memory, ends stuck background services, and resets the state that accumulated over days of uptime. Android and iOS both run better after a restart when they have been up for a week or more. Do it before you open the problem app rather than after the crash, and see whether the crash still happens on a freshly booted device.

On a computer the equivalent check is Task Manager on Windows (Ctrl+Shift+Esc, Performance tab, Memory) or Activity Monitor on macOS (Applications, Utilities). If memory sits above roughly 90 percent before the crash, close the heaviest processes and retest. A browser with forty tabs open will crash the tab, and sometimes the browser, and the fix is closing tabs rather than reinstalling the browser.

Reinstall the App Cleanly and Restore Your Data

Uninstall, restart the device, then reinstall from the official store. The restart between steps matters: it clears leftover files the uninstaller leaves behind, which is exactly the corrupted state you are trying to remove. On Android: Settings, Apps, select the app, Uninstall. On iOS: long-press the icon, Remove App, Delete App. Then reboot and install fresh.

Confirm your data survives before you delete anything. Games and social apps usually sync to an account; note-taking and photo-editing apps often do not. On Android, check Settings, Google, Backup, and confirm the app is listed as backed up. On iOS, check Settings, your name, iCloud, iCloud Backup, and confirm the last successful backup date — anything from the last 24 hours is a safe restore point.

Reinstalling fixes a specific class of crash that nothing else touches: a corrupted app binary, a half-finished update, or a data file the app can no longer parse. If the app crashed on launch and survived a cache clear, reinstall is the next honest step, and it costs about five minutes plus download time. Do not skip the restart — a reinstall over the old install can reproduce the same fault.

Track what you lose. Sign-ins come back quickly with a password manager. Local saves do not come back at all if they were never synced. Before reinstalling a game, check whether it stores progress on the device or on the developer's servers; most mainstream games sync, but a surprising number of smaller ones do not, and the store listing rarely says so outright.

Fix Crashes Caused by Permissions, Battery Savers, and Overheating

Permissions cause a narrow, repeatable crash: the app dies the moment it tries to use the camera, microphone, location, or storage and finds the permission denied. Grant or revoke deliberately. Android: Settings, Apps, select the app, Permissions. iOS: Settings, scroll to the app, and toggle the specific permission. Test the exact action that crashed before you touch anything else.

Battery savers are the second hidden cause. Aggressive power management suspends background apps, and an app that expects to keep running dies when it is frozen mid-task. On Android, Settings, Battery, Battery optimization lets you exempt a specific app. On iOS, Settings, Battery, Low Power Mode is the switch to check. If the crash only happens when the phone is below 20 percent, this is your answer.

Heat is the third. Both platforms throttle the processor and dim the screen when the device gets hot, and a heavy app can be killed outright. If the crash follows ten minutes of gaming, video recording, or navigation in direct sun, let the phone cool to room temperature before retesting. A case that traps heat, or charging while gaming, makes it worse — remove the case and unplug during the test.

Testing one variable at a time is what turns this section from guesswork into diagnosis. Change the permission, retest the same action. Exempt the app from battery optimization, retest the same scenario. Cool the device, retest the same load. If exactly one change makes the crash stop, you have found the cause and can decide whether to live with the workaround or report it to the developer.

Match the Workaround to Your Platform and App Type

The same crash needs different handling depending on where it happens. Use the table below as a quick reference; the specifics behind each row are what matter when a general fix has already failed.

Platform or app type Most likely cause First action Where the setting lives
Android phone, any app Corrupted cache or stale install Clear cache, then force-stop Settings, Apps, app, Storage
iPhone or iPad Corrupted install after update Offload app, reinstall from App Store Settings, General, iPhone Storage
Windows desktop app Full system drive or broken runtime Free 10–15% of C: drive, then repair the install File Explorer, C: Properties
macOS app Corrupted preferences or permissions Reset the app's saved state and re-grant access System Settings, Privacy & Security
Mobile game Memory pressure or unsynced local save Confirm cloud sync, then reinstall In-game account settings
Banking or payment app Outdated version or blocked permission Update the app, verify permissions App store listing, then app settings

The banking row deserves a caveat. Financial apps add their own integrity checks, and some refuse to run on rooted or jailbroken devices, or on devices with certain accessibility services enabled. If a banking app crashes on launch while everything else works, check the app's own support page for device requirements before you reinstall — the crash may be intentional.

Desktop apps fail differently from mobile ones. A Windows application that crashes on launch often needs a repair rather than a reinstall: Settings, Apps, Installed apps, select the app, Advanced options, Repair. That rebuilds the installation without touching your data. On macOS, deleting the app's preferences file from Library, Preferences and relaunching resets the state that a corrupted setting broke.

Games sit in their own category because they push memory and graphics hardest. Lower the in-game graphics settings before reinstalling — resolution scale and shadow quality are the two heaviest. If the crash stops at lower settings, the device is being asked for more than it can hold, and no reinstall will change that.

Know When to Factory Reset or Escalate

A factory reset is the last user-side step, and it should be earned. Reach it only when multiple unrelated apps crash, a reboot does not help, and the storage and memory checks came back clean. Back up first: Android through Settings, Google, Backup; iOS through iCloud Backup or a computer. The reset itself lives at Settings, System, Reset options on Android and Settings, General, Transfer or Reset iPhone on iOS.

Time the decision honestly. A reset costs an hour or more to restore apps, sign-ins, and settings, and it fixes a system-level corruption that no other step reaches. If one app crashes and everything else is stable, a reset is the wrong tool and will not help. If the phone crashed during the setup screen after a reset, the fault is in the hardware or the firmware, and the next stop is the manufacturer.

Escalate to the developer before you escalate to a reset in most cases. The crash report you took in section two contains the package name and the failure, and support teams use it. Include the app version, the OS version, the device model, and the exact action that triggers the crash. That is the same information a service center will ask for.

Warranty and repair are the final rung. Repeated crashes that survive a reset point at failing storage or memory hardware, and the fix is a service visit rather than a setting. Check the device's warranty status with the manufacturer using its serial number before paying for a repair — coverage periods vary by country and by purchase date, so confirm on the maker's site rather than assuming.

FAQ

Why does an app crash only when I open the camera inside it?

That pattern almost always means the camera permission is denied or the camera is already held by another app. Grant the permission in Settings, then close any app that might be using the camera in the background, and retest. On Android, Developer options also shows whether a camera service is stuck.

Can clearing the cache delete my photos or messages?

No — a cache clear removes temporary files only, and your photos, messages, and account data stay put. Clearing app data is different: it resets the app to a fresh install and can remove locally stored content that never synced to an account. Check for cloud sync before you use the data-clear option.

Why do crashes start right after a system update?

Updates reset app permissions and can leave old files in a format the new OS no longer reads, so an app that was fine yesterday fails today. Reinstalling the affected app usually resolves it because the fresh install writes current-format data. If several apps fail after the same update, check the manufacturer's support page for a known issue before doing anything else.

Does reinstalling an app delete my game progress?

It depends entirely on whether the game stores progress on its servers or on the device. Mainstream titles with account sign-in sync progress and restore it on reinstall; smaller offline games often do not, and the store listing rarely says which. Confirm cloud sync inside the game's account settings first — that check costs a minute and prevents a lost save.

Is it worth paying for a repair if the phone crashes after a factory reset?

Yes, because a crash that survives a reset points at hardware — failing storage or memory — and no further software steps will fix it. Check warranty status with the manufacturer using the serial number before paying, since coverage varies by country and purchase date. A service center will run the same diagnosis you just did and confirm the failing component.

Can a full storage drive really cause crashes with no error message?

Yes, and it is one of the most common causes. Apps need scratch space to write temporary files while running, and when the drive has no room those writes fail and the app exits, often silently. Keep at least 1 GB free on a phone and roughly 10–15 percent of the system drive free on a computer.

Why do only some apps crash on my phone while others are fine?

An app-specific crash narrows the cause to that app's install, permissions, or version compatibility rather than the device itself. Start with a force-stop and cache clear for that app, then check its version against the latest release. If two unrelated apps crash together, switch to the system-level checks instead.

How often should I restart my phone to prevent crashes?

A restart every week or so clears leaked memory and stuck background services that accumulate with uptime, and it is the cheapest preventive step available. Both Android and iOS run more reliably after a reboot following days of continuous use. Restart before opening a problem app rather than after it crashes.

Crashes that trace back to a failing drive or a hardware fault on a work device are worth raising with whoever manages that device before you reset anything yourself, since some organizations restrict user-initiated resets.