How to fix app crash after install on Android

Likely causes of post-install crashes

Most immediate crashes fall into one of these categories:

• Corrupt or incomplete APK — the file was damaged during download or transfer.
• Insufficient storage — the app installed but cannot unpack assets or create its data directory.
• Stale cache from a previous version — leftover data conflicts with the new build.
• Permission denial at runtime — the app requests a permission it cannot obtain and fails to handle the denial.
• Battery optimization killing the process — the system terminates the app before it finishes initialising.
• Version or architecture incompatibility — the APK targets a higher API level or a different CPU architecture than your device supports.

Work through the sections below in order. Each step eliminates one category before moving to the next.

Step 1 — Clear cache and app data

If you are reinstalling or updating an app, leftover cache from the previous version can cause conflicts. This is the fastest fix and should be tried first.

1. Open Settings > Apps (or App management on ColorOS).
2. Find and tap the crashing app.
3. Tap Storage & cache (or Storage usage).
4. Tap Clear cache. Launch the app again.
5. If the crash persists, return to the same screen and tap Clear data. This resets the app to its initial state—saved logins, local files, and preferences are deleted.

Note: Clearing data is destructive. If the app syncs to a cloud account, you can sign in again after clearing. If it stores data only locally (offline games, downloaded maps), that data is lost.

Step 2 — Check available storage

Some apps install successfully but crash on first launch because they need to unpack additional assets (game data, ML models, offline databases). If internal storage is nearly full, this extraction fails silently.

Go to Settings > Storage and confirm at least 1–2 GB of free space beyond the app's listed size. If storage is low:

• Clear cached data from other large apps (video streaming apps often cache hundreds of megabytes).
• Move photos and videos to cloud storage or an SD card.
• Uninstall apps you no longer use.

After freeing space, uninstall the crashing app, then install it again to ensure a clean extraction.

Step 3 — Review permission conflicts

Android 11 and later enforce scoped storage, one-time permissions, and auto-revocation of unused permissions. An app that worked on Android 10 may crash on Android 13 if it does not handle permission denials gracefully.

Check the app's permissions at Settings > Apps > [App name] > Permissions. Look for permissions that are set to "Deny" or "Ask every time." If the app crashes immediately after you deny a permission prompt, that permission may be essential to its startup sequence—granting it is the only workaround until the developer releases a fix.

Common offenders:

• Storage / Files and media — apps that need to read or write local files.
• Location — delivery, transport, and weather apps that initialise a map view on launch.
• Phone — some older apps check the device ID at startup and crash if phone permission is denied.
• Display over other apps — overlay-dependent apps (screen recorders, floating widgets) need this special permission enabled in Settings > Apps > Special app access > Display over other apps.

Step 4 — Check battery optimization settings

ColorOS, OxygenOS, and other manufacturer skins apply aggressive battery restrictions that can terminate apps during initialisation—especially apps that perform lengthy background setup on first launch (syncing contacts, indexing files, downloading configurations).

To exempt the app from battery optimization:

1. Go to Settings > Battery > More battery settings > Optimize battery use.
2. Find the crashing app and set it to Unrestricted (or "Don't optimize").
3. On ColorOS, also check Settings > App management > [App name] > Autostart and enable it if the app needs to run a service at boot.

For a deeper overview of how these settings interact, see ColorOS battery optimization guide.

Step 5 — Verify version compatibility

An APK can install successfully but crash at runtime if it requires a higher Android version than your device runs. This happens because the installer checks minSdkVersion but the app may call APIs available only in its targetSdkVersion.

Check your Android version at Settings > About phone > Android version. Then check the app's requirements on the developer's download page or store listing. If your device is below the minimum supported version, no fix exists other than upgrading the OS (if an update is available) or using an older release of the app.

CPU architecture mismatch

APKs contain native libraries compiled for specific CPU architectures. A 64-bit-only device cannot run an APK that contains only 32-bit (armeabi-v7a) libraries, and vice versa. The install may succeed, but the app crashes when it tries to load the native code.

If the developer provides multiple APK variants (arm64, universal), download the one matching your device. You can check your CPU architecture at Settings > About phone > CPU or by searching your model number online.

Step 6 — Reinstall from a clean download

If none of the above steps resolve the crash, the APK file itself may be corrupt or incomplete.

1. Uninstall the app completely (do not just "update" over it).
2. Delete the downloaded APK file from your Download folder.
3. Re-download the APK on a stable Wi-Fi connection. Avoid mobile data in areas with poor signal—interrupted downloads produce truncated files that may still install but crash at runtime.
4. If the developer publishes a SHA-256 checksum, verify it before installing. See Check APK file integrity for instructions.
5. Install the fresh APK and launch it.

Step 7 — Capture a crash log (advanced)

If the crash persists through all steps above, a crash log helps the developer diagnose the problem. To capture one:

1. Enable Developer options by tapping Build number seven times in Settings > About phone.
2. In Developer options, enable USB debugging.
3. Connect the device to a computer and run:

   adb logcat -s AndroidRuntime:E ActivityManager:W

4. Launch the crashing app. The terminal will display the exception type and stack trace.
5. Copy the relevant lines (starting from FATAL EXCEPTION) and include them when reporting the bug to the developer.

Edge cases and common mistakes

• Installing an update over a different-signed build: If you previously installed a debug or third-party build and then try to update with the official release (or vice versa), the signatures conflict. The install may succeed on some devices but crash immediately. Uninstall the old version first, then install the new one. You will lose local data.
• Split APKs missing components: Some apps are distributed as split APKs (base + configuration APKs). Installing only the base APK can result in missing resources—the app launches but crashes when it tries to load a missing density or language pack. Use a bundle installer or adb install-multiple to install all splits together.
• WebView crashes after a system update: Android System WebView is a shared component. If a system update ships a broken WebView version, every app that embeds a web view crashes. Check for a WebView update in the Play Store, or open Settings > Apps > Android System WebView and tap Uninstall updates to revert to the factory version.
• Assuming the phone is faulty: A crash in one app almost never indicates a hardware defect. If multiple unrelated apps crash after an OS update, try clearing the system cache partition from recovery mode (this does not erase personal data). A factory reset is a last resort and should not be attempted without backing up first.
• Reinstalling without clearing data: Uninstalling and reinstalling does not always remove the app's data directory on every device. If stale data is the cause, the crash recurs. Explicitly clear data before uninstalling, or verify that the data folder is gone at /storage/emulated/0/Android/data/[package.name].

Note: If you sideloaded the APK, verify you are downloading from the developer's official channel. Repackaged APKs from third-party mirrors may contain modified code that causes crashes or unexpected behaviour. See How to install APK files safely for source verification guidance.