You tap an app icon and the app opens for a second and then it closes without warning. You tap it again and the same crash happens at the same screen. That pattern is maddening because the app worked yesterday and you need it today.
Apps crash on launch when they cannot load a corrupt file or when they run out of memory or storage. A bad update can introduce a bug that crashes the app before it shows content. Low free space can also stop an app from creating files it needs at startup. App crashes and system freezes share early warning signs, and a System UI is not responding popup often points to the same overloaded state behind both.
This guide gives you five steps in a safe order. Each step protects your data as much as possible. Test the app after each step and stop when it opens normally.
Step one restart and update the app
Restart the phone to clear a stuck process that the app depends on. A restart is fast and it fixes many one-time crashes. Open the app after the restart and note whether it still crashes at the same point.
Check for an app update in the store and install it if one is available. Developers fix crash bugs quickly after a bad release. An update can fix a crash that no setting on your phone can fix.
Check for a system update as well if many apps crash at once. A system bug can break several apps together. When many apps crash together the system is more suspect than any single app.
Step two clear cache without losing data
Open Settings and then open Apps and then open the crashing app and then open Storage. Tap Clear cache and test the app again. Cache clearing removes temporary files and it keeps your login and your saved data.
Do not tap Clear data at this stage. Clearing data logs you out and removes app settings and offline files. Save that step for later after you have backed up anything important inside the app.
Check free storage on the phone while you are in settings. Free at least a few gigabytes if the phone is nearly full. An app that cannot write a startup file will crash even when its own cache is clean.
Step three check permissions and WebView
Open app permissions and make sure the app has the permissions it needs to start. A denied storage or network permission can crash an app that expects access at launch. Grant only the permissions that make sense for that app.
Update Android System WebView if the crashing app shows web content. Many apps embed web views for login screens and feeds. An outdated WebView can crash those apps at launch. Update it from the store and restart the phone after the update.
Test the app on Wi-Fi and on mobile data separately. A network fault can look like a crash when an app fails to load its first screen. If the app opens on one network but not the other then the network is part of the problem. If notifications also arrive late then the steps for fixing delayed notifications on Android can help you check background restrictions that affect apps.
Step four reinstall as a clean fix
Uninstall the app only after cache and update tests fail. Reinstalling replaces corrupt app files with a fresh copy. Back up chats or files inside the app first if the app offers export.
Install the app again and open it before restoring a backup. If the fresh app works then the old install was corrupt. Restore your data slowly and watch for a backup file that reintroduces the crash.
Check app reviews for crash reports from other users on the same version. If many users report the same crash then waiting for a developer fix beats repeated reinstalls. Report the crash through the store so the developer sees your device details.
Step five test in safe mode
Boot into safe mode if the app still crashes after reinstall. Safe mode disables third-party apps that might interfere with it. If the app works in safe mode then another app is interfering with it.
Uninstall recently installed apps one by one in normal mode. Start with apps that overlay other apps or manage battery aggressively. Those apps can kill or block other apps at launch.
Consider a factory reset only when many apps crash and safe mode also fails. Back up everything first and restore slowly. A reset is a last step not a first step.
adb shell pm clear com.example.app
adb shell dumpsys package com.example.app
adb logcat -d | grep -i crash
The commands above were prepared for this guide and they use only standard tools that ship with Android developer tools. They show package state and crash clues for advanced users and they use a placeholder package name that you replace with the real app package.
While you work through these steps it helps to compare symptoms with other fixes in the same area. For example the steps for delayed notification problems show how a related fault behaves differently and the steps for random restart problems help you rule out a second fault that shares early symptoms.
Common mistakes
One common mistake is clearing data before clearing cache. Clearing data loses login and settings for a problem that cache clearing could fix. Another mistake is reinstalling the app five times without restarting the phone once.
Another mistake is ignoring low storage. Users blame the app while the phone has almost no free space left. Freeing space often fixes several crashing apps at once.
A third mistake is installing an old version from an unknown source to avoid a crash. That version can carry security risks and it can break with newer system services. Stay with store versions unless you have a clear reason to change.
A week-long app stability test that proves the fix
Open the crashing app at the same time each day for a week and note whether it opens and how far it gets before a crash. A crash at the same screen each day points to a specific content or login step. A crash at random screens points to memory or storage pressure. That pattern guides the next fix far better than a vague report that the app crashes.
Test the app after a restart on day three and compare it with tests without a restart. A restart that fixes the app for a day points to a stuck background process. A restart that changes nothing points to corrupt app data or a developer bug.
Test the app on Wi-Fi and on mobile data on separate days. A network-dependent crash can look like a pure app crash when the first screen needs data. If the app opens on one network but not the other then network settings or a blocked service deserve attention.
Long-term habits that protect app stability
Keep free storage above a few gigabytes so apps can create startup files reliably. A phone that fills up gradually will start crashing apps one by one. A monthly storage check prevents that cascade.
Update apps promptly but read recent reviews after a major app update. A wave of crash reports after an update signals a developer bug that reinstalls will not fix. Waiting for the next patch saves repeated reinstall effort.
Limit aggressive battery optimisation for apps you rely on daily. An optimiser that kills an app in the background can cause a crash on next launch. A balanced setting keeps daily apps stable without draining the battery.
What to do when an app still crashes after reinstall
Check the app developer page for known crash reports on your phone model. A model-specific crash may need a developer patch rather than user fixes. Reporting your model and version helps the developer reproduce the bug. A patch for a specific model can take longer than a general fix.
Test the app with a different account if it supports multiple accounts. A corrupt account sync can crash an app at launch for one account only. A second account that works cleanly points to account data rather than app files.
Check whether a VPN or ad blocker interferes with the app startup. A blocked network request at launch can crash an app that expects a response. Disable the VPN for one test and see whether the app opens normally.
Keep a note of the exact crash screen and error message for support. A screenshot of the crash point helps support identify the failing step. Vague reports take longer to resolve than reports with a screen and a time.
Testing a crashing app with a second account and a second network
Test the app with a second account if the app allows it and note whether the crash follows the account. An account-specific crash points to corrupt sync data for that account. A crash for both accounts points to app files or system causes. That test is quick and it prevents unnecessary reinstalls.
Test the app after clearing only its cache on a second day and compare with a day without cache clearing. A cache test that improves stability for a day points to cache corruption that returns. A cache test that changes nothing points to deeper app or system faults.
Test the app on a tablet or a second phone if you have access to one. A second device test separates device-specific bugs from general app bugs. An app that crashes on two devices points to a developer bug. An app that crashes on one device points to that device setup.
Test the app with a VPN disabled and with an ad blocker disabled on separate days. A network tool can block a startup request and cause a crash that looks like an app bug. Disabling those tools one at a time reveals the interfering tool clearly.
Test the app immediately after a restart and after a full day of use. A crash that appears only after a full day points to memory pressure building up. A crash immediately after a restart points to a startup bug that does not need time to develop.
Keep a note of the app version for every crash test. A version change can fix or introduce a crash without any setting change on your phone. Version notes help you link a new crash pattern to a specific update.
Frequently asked questions
Why does only one app crash while others work fine?
A single app crash usually points to that app cache or update or data. System faults tend to break many apps together. Focus on that app cache and update first.
Will clearing cache delete my photos in the app?
No because cache holds temporary files only. Your photos and chats live in app data or cloud storage. Clearing data is the step that can remove local app files.
How do I know if a crash is a developer bug?
Check recent reviews and see whether other users report the same crash on the same version. A sudden wave of reports after an update points to a developer bug. A fix usually arrives in the next update.
Conclusion
Apps that crash on launch usually recover with a restart and an update and a cache clear in that order. Check storage and WebView before you reinstall and test in safe mode before you reset the phone. Keep a backup before clearing data or reinstalling. If a fresh install still crashes in safe mode then report the crash and wait for a developer fix. Start today by restarting the phone and clearing the cache of the crashing app.
