Android App Keeps Crashing: 9 Fixes in Safe Order

Use nine fixes from least disruptive to most disruptive

When one Android app keeps crashing, first prove that other apps and the phone still work. Then try these nine fixes in order: restart the phone; update the app; update Android; check storage and connection; force stop the app; review permissions and automatic time; clear cache; clear app storage; uninstall and reinstall. Stop as soon as the app works, because troubleshooting is not a loyalty programme.

Clearing storage and reinstalling can erase local app files, drafts, downloads, sessions, settings, and progress. Back up or export what you can and verify credentials before fixes 8 and 9.

First, define the failure

Write down what happens:

• Does the app close immediately, freeze on one screen, or crash after one specific tap?
• Did it begin after an app update, Android update, account change, or new download?
• Do other apps open normally?
• Does the app fail on Wi-Fi, mobile data, or both?
• Is the service itself reporting an outage?

If many unrelated apps crash or the phone restarts, skip app-level deletion and investigate the device. If only one web-dependent app fails, check the connection with the Wi-Fi connected without internet guide.

Google’s current installed-app troubleshooting guidance follows the same broad escalation: restart and update first, then force stop, cache or data actions, and uninstall only later. It also warns that settings vary by phone.

Fix 1: restart the phone

Use the device’s normal restart command. On many Android phones, hold the power button and choose Restart; button combinations differ on some models. If the screen is frozen, consult the manufacturer’s exact restart instructions rather than guessing a factory-reset combination.

After restart, open only the affected app and repeat the smallest known failure. If it works, stop. If it crashes, record that restart was tested.

A restart clears temporary processes and reloads system services without deleting personal data. It is boring, reversible, and therefore deserves to go before “delete everything and discover your password archaeology.”

Fix 2: update the app from its official listing

Open Google Play, tap the profile icon, then use Manage apps & devices on current common versions. Look for the affected app under available updates. Interface wording can vary by Play Store release.

Read recent release notes if available and confirm the listing is the same developer and app you already use. Do not install a package from a search result or third-party download site to “roll back”; unofficial packages can be modified and may expose accounts or data.

After update, restart and test the exact action again. If the crash began with the latest update and no newer patch exists, collect evidence for the developer rather than repeatedly clearing unrelated phone settings.

Fix 3: update Android and system components

On many phones, open Settings > System > Software update or System update; some makers put it under About phone. Install supported updates only when the battery, power, network, and available storage meet the device maker’s requirements.

Also check Google Play system update if the phone exposes it, commonly under security or device-information settings. Do not force an unsupported operating-system image onto the device.

Restart after updates and test. If the phone is no longer receiving compatible software and the app requires a newer Android version, the durable answer may be a supported device or the developer’s web version—not an invented hidden setting.

Fix 4: check storage and the connection

Look at available device storage in Settings; the path may be Storage, Battery and device care > Storage, or another manufacturer label. If storage is nearly exhausted, remove known downloads or unused media after backing them up. Avoid cleaner apps promising secret access.

Then compare connections. If the app needs the web, test one ordinary website. Switch from Wi-Fi to mobile data or another authorised network, accounting for data charges. If everything fails on one Wi-Fi network, troubleshoot that network instead of the app.

Check whether battery saver, data saver, or background restrictions apply to the app. Paths and effects vary, so inspect the app’s official support page before granting unrestricted background use. Do not weaken device security merely because a forum said “turn everything off.”

Fix 5: force stop the app

On many Android versions, open Settings > Apps > See all apps > app name, then choose Force stop and confirm. A long-press on the app icon may also expose App info.

Force stop ends the current app process. It does not normally erase the app’s stored account or files, although unsaved work in the active session can be lost. Reopen and reproduce the issue.

If the app is performing a critical upload, payment, navigation session, device update, or health/accessibility function, understand the consequences before stopping it.

Fix 6: review permissions, date, and account scope

In the app-info page, inspect Permissions. Grant only permissions necessary for the failing feature. A camera app may need camera access; a calculator does not need your contacts as a spiritual preference.

If the failure occurs at sign-in, confirm the phone uses automatic date, time, and time zone. Authentication can fail when the clock is wrong. On many phones the path is Settings > System > Date & time, but manufacturer labels vary.

Check whether the same account works on the service’s official website or another device. Do not remove the account from the entire phone until you know what locally synchronised data and authentication methods would be affected.

Fix 7: clear only the cache

Open Settings > Apps > app name > Storage & cache on many current Android phones and select Clear cache. Some makers call the page Storage. Read the buttons carefully: Clear cache and Clear storage/data are not interchangeable.

Cache is temporary app material and normally rebuilds. Clearing it can resolve a damaged temporary file without resetting the whole app. Reopen, wait for necessary content to reload, and test.

This may briefly increase data use and loading time. If the app works, stop. The cache returning later is expected; cache is not a mould infestation.

Fix 8: clear app storage only after backup

Destructive app-level step: Clear storage, Clear data, or similar wording resets local app state. Before tapping it:

• Confirm the account email or username.
• Verify the password and multi-factor method.
• Export local drafts, recordings, files, or keys where the app permits.
• Confirm cloud synchronisation from the service itself.
• Understand whether offline downloads or game progress will return.

Then use the app-info storage page and read the confirmation screen. Set the app up again and test before restoring large downloads.

Do not clear data for an authenticator, password manager, wallet, medical device app, or workplace app without its exact recovery process. “Probably synced” is not a backup status.

Fix 9: uninstall and reinstall from the official store

Destructive app-level step: uninstalling can remove the app and its local data. Complete the same backup and credential checks as fix 8. Then uninstall through App info or the official Play Store listing and restart the phone.

Reinstall from the verified listing, grant only required permissions, sign in, and test the original failure before importing optional content. If the app is no longer listed or compatible, do not sideload a mystery copy to preserve routine.

If reinstall still fails while other apps work, contact the developer. Include app version, Android version, phone model, time, exact reproduction steps, connection type, and fixes attempted. Redact personal information from screenshots and logs.

If several apps fail, change the diagnosis

When unrelated apps crash, check device storage, Android updates, overheating, recent downloads, and whether the phone behaves in manufacturer-documented safe mode. Safe-mode entry varies by model and temporarily disables downloaded apps; use the maker’s support guide.

Back up important data. Hardware damage, liquid exposure, battery swelling, extreme heat, repeated restarts, or a blank screen calls for authorised repair or manufacturer support.

A factory reset erases device data and should not be a routine tenth item. If official support ultimately recommends it, verify a complete backup, account credentials, authenticator recovery, eSIM or carrier needs, and device-specific restoration instructions first.

Keep a small evidence log

Record:

That log makes developer support useful and prevents you from repeating fix 4 at midnight because the menu looked new.

If storage caused the problem on an Apple device instead, use the separate iPhone storage guide. If a peripheral—not an app—is failing on a PC, follow the Windows Bluetooth checks rather than applying mobile fixes to a driver problem.