APK Update Failed? How to Fix It on Android in 2026
You tap Update and Android refuses — 'App not installed,' 'Package conflicts with an existing package,' or it hangs. Almost every failed APK update comes down to a handful of causes: signature mismatch, insufficient storage, a leftover version, a corrupted or split-APK download, install-source permissions, or a stale package installer. This guide matches each error message to its exact fix, for both Play Store and sideloaded apps.
You tap Update and Android refuses: "App not installed," "Update failed," "Package conflicts with an existing package,"or the install just spins forever and dies. You've already restarted the phone. Still broken.
Here's the good news: failed APK updates almost always come down to a small set of causes.Match your exact error message to the cause below, apply the fix, and you'll get past it. The trick is that each error means something slightly different.
The core rule: read the exact error text — it names the cause."Signature mismatch," "insufficient storage," and "conflict" are three different problems.
1. Identify your error first
Grab the exact wording before doing anything:
- "App not installed" → generic; usually a leftover version, storage, or signature issue.
- "Package conflicts with an existing package" → signature mismatch. Big one.
- "Update failed" / "Installation failed" → often storage or a corrupted download.
- "Insufficient storage"→ you're out of space (the real fix below, not just "delete a photo").
- Install hangs / spins forever → install source conflict or a stuck package.
Match yours to the sections below.
2. Cause #1: signature mismatch (the most common)
Symptom:"Package conflicts with an existing package," or "App not installed" when updating.
Why: Android will only update an app if the new APK is signed with the same certificate as the installed one. If you installed the app from Google Play and now try to update with an APK downloaded from elsewhere (or vice versa), the signers differ — and Android blocks the update.
Fixes:
- Update from the same source you installed from. Play-installed → update via Play. Sideloaded → update with an APK signed by the same key.
- Uninstall the old version, then install the new one. This wipes app data, so back up first. After that, use one consistent source going forward.
- If you need to keep data:you can't cross signers without root. Migrate data first, then clean-install.
Tip: this is exactly why some "modded" or repackaged APKs won't update over the official app — different signature by design.
3. Cause #2: not enough storage
Symptom:"Insufficient storage" or "Update failed" late in the process.
Why: Android needs free space for the new APK + extraction + the old version still present during the update. A 200 MB app can need 400–600 MB free to update.
Fixes:
- Check Settings → Storage for real free space.
- Free up at least 2× the app's size. Delete caches, old downloads, unused apps.
- Empty the Play Store cache: Settings → Apps → Google Play Store → Storage → Clear cache.
- Retry. If it fails at 90%, it's almost always storage.
4. Cause #3: leftover / conflicting version
Symptom:"App not installed" with plenty of storage, sometimes after a failed attempt.
Why:A half-installed package, a "work profile" copy, a pre-installed system version, or an app cloned/dual-app instance is blocking the new install.
Fixes:
- Uninstall the existing version completely(including any "dual app" clone).
- Check for copies under Settings → Apps — look for the same name in a work profile or secure folder.
- If it's a system app (pre-installed, can't uninstall), uninstall its updates first: app info → ⋮ → Uninstall updates. Then install the new APK.
- Reboot and retry.
5. Cause #4: corrupted or incomplete download
Symptom:"App not installed" / "There was a problem parsing the package."
Why:The APK got truncated, or a "split APK" (App Bundle) was downloaded as a single file. Modern apps ship as split APKs (base + config splits); installing the base alone fails.
Fixes:
- Re-download the APK — the file is likely corrupt.
- If it's a split/app-bundle app, download a proper XAPK or APKS bundle, and install it with a tool that handles splits (e.g., an XAPK installer or
adb install-multiple). - Verify the file isn't 0 bytes and matches the expected size.
6. Cause #5: install source / permissions
Symptom: Install hangs or the button does nothing.
Why: The app you're installing from(Files, browser, chat app) lacks the "install unknown apps" permission, or Play Protect blocks it.
Fixes:
- Settings → Apps → [the app opening the APK] → Install unknown apps → allow.
- Temporarily pause Play Protect scanning (Settings → Play Store → Play Protect).
- Retry from a plain Files app to rule out the opener.
7. Cause #6: stale package installer state
Symptom: Everything looks fine but installs silently fail.
Fixes:
- Settings → Apps → Google Play Store and Package installer → Clear cache (and data for Play Store if needed).
- Reboot the phone.
- Retry.
8. Quick decision table
- Package conflicts with existing → Signature mismatch → Same-source update / uninstall+reinstall
- Insufficient storage → Space → Free 2× app size, clear caches
- App not installed → Leftover version / clone → Uninstall fully, check work profile
- Problem parsing package → Corrupt / split APK → Re-download / use XAPK
- Install hangs → Missing permission → Enable install-unknown-apps
- Silent failure → Stale installer → Clear Play Store cache, reboot
9. FAQ
Q: Will uninstalling lose my data? Yes, uninstalling clears app data. Back up (in-app export, cloud sync, or adb backup where supported) first.
Q: Can I update across different signers without losing data?Not without root. Cross-signer updates aren't allowed by Android's design.
Q: Play Store update fails but sideloading works — why? Usually a Play Store side issue (cache/account). Clearing Play Store cache and retrying typically fixes it.
Q: It works after a reboot, then fails again. A background package manager or clone service is re-conflicting. Check for dual-app / work-profile copies.
Bottom line: failed APK updates aren't random — the error names the cause. Signature mismatch → same source or clean reinstall. Out of space → free 2× the size. Leftover version → uninstall fully first. Corrupt/split APK → re-download the right format. Match your message to the fix above and you'll update cleanly every time. For related fixes, see our install-block troubleshooting guide.