“App not installed” is the most useless message Android has: a dozen different installer refusals hide behind it. But if you're installing an APK over an app that's already installed from Google Play, the cause is almost always the same one — a signature conflict. In the logs it's INSTALL_FAILED_UPDATE_INCOMPATIBLE, “signatures do not match”. Let's start with it, because it's both the most common and the most baffling.

Signature conflict: how it works

Every APK is signed with the publisher's cryptographic key. Android remembers the fingerprint of that key for good on the first install, and after that allows an update only with the same fingerprint. This is protection against substitution: otherwise anyone could “update” your banking app with their own build.

So a file signed with a key other than the one on the app you have installed will never install — not with a reboot, not with clearing the cache, not with Play Protect disabled. Updating over it is physically impossible.

How to check in a minute

If both answers are “yes”, it's a signature conflict. If the app isn't on the phone at all, the cause is different — scroll down.

Honestly: where things stand with our files

This applies to AppLoko too, so we'll say it plainly, with no evasive wording. Most of the catalog is assembled from sets of parts (split APKs) that Google Play delivers to the device. To make such a set installable with a normal tap, the parts were merged into a single APK — and merging kills the publisher's original signature, so the file was re-signed with our key.

A measurement of the production database on 10.09.2026: 972 of 1031 cards have the same value in the certificate fingerprint — 7a1d8996…a050. Among them are Telegram, WhatsApp Business, Signal, Brave, AliExpress, Candy Crush Saga, Yandex Maps. Hundreds of independent publishers can't share one certificate: this is our key. Another 58 cards kept their original signatures — they have 56 different fingerprints, and such files do install over Play normally.

The certificate fingerprint and SHA-256 are printed on the card before downloading, on the version page. If it shows 7a1d8996…, the file is our rebuilt one, and it won't install over the version from Play.

What to do in this case

  1. Update from the store the app came from. The most boring and the most correct path, if the app works for you.
  2. Delete the old version and install ours. It always works, but the app's data will be deleted along with it: chats, game progress, local settings. Export or back up first — in messengers this is a separate item in the settings, and you must do it BEFORE deleting.
  3. Wait for the card in its original packaging. We're moving the catalog to distributing the original set of parts in a .xapk container, with no merging and no re-signing — such files do install over Play. As of 10.09.2026, 7 of 1031 cards are served this way; the rest are still in the old form.

One nuance that saves time: you need to delete the app itself, not “clear data”. Clearing data doesn't touch the certificate fingerprint, and the error will repeat word for word.

If the app isn't on the phone — the other causes

Not enough space

The installer needs roughly two to three times the file's size: the APK itself, the unpacked code and the data. The median file in the catalog is 61.8 MB, but 297 of 1031 are heavier than 100 MB. Free up a gigabyte or two and try again; you can't delete the APK itself before the installation finishes.

The same package is already taken by another app

Clones, “dual accounts” and work profiles install an app with the same package name. It isn't visible on the phone, but the installer sees it and refuses. Check secondary spaces and the work profile.

Play Protect blocked the installation

Then the message will have a separate line about a “harmful app” or an “app from an unknown source”. That's a different failure, not about the signature.

The build itself doesn't fit the phone

The Android version is lower than required or the CPU architecture is different. We cover this in detail in the article “Not supported on this device”. In short: 183 apps in the catalog install on Android 6.0 and below, 533 — on Android 7.0 and below, and 251 builds are compiled only for 64-bit arm64-v8a.

The file is corrupted

An APK that was under-downloaded or modified after signing gives the same faceless “App not installed”. Compare the SHA-256 from the card with the hash of the downloaded file — see “Package is invalid”.

What to do if nothing helped

  1. Reboot the phone — it clears a hung installation session.
  2. Download the file again over Wi-Fi, straight from the card, without a download manager.
  3. Check free space and delete the old version of the app.
  4. Make sure the “Install unknown apps” permission is granted to the app you're opening the file from.

If the error sounded different — see “There was a problem parsing the package” or the general checklist “APK won't install”.