You tap Update. The button spins, then goes back to saying Update. Or the download runs to the end and reports that the app was not installed. Either way, the version on your phone stays exactly where it was.
Updates fail differently from first installs, and they fail for reasons a fresh install never hits — because an update has to replace a package that is already there, signed by the same key, without destroying the data inside it. There are more ways for that to go wrong.
First, read what the failure actually says
Android hides the useful part of the message behind a generic one. The code that appears briefly, or in the notification shade, narrows the cause down enormously.
| What you see | What it usually means | Go to |
|---|---|---|
| Error 963 / 919 / 492 | Cache or storage trouble on the phone | Fixes 1 and 2 |
| Error 505 / “App not installed” | A conflict with the installed copy | Fix 5 |
| Error 403 / 491 | Account or region mismatch | Fix 4 |
| Nothing at all, button just resets | Queue, network preference or storage | Fixes 1 to 3 |
| “Update” is greyed out or missing | Managed device, or the update is staged | Fix 6 |
Fix 1: Clear the Play Store’s cache, then Play Services
The Play Store keeps a local record of what version you have and what version it thinks is available. When those two disagree with reality, the Update button does nothing at all.
- Settings → Apps → See all apps → Google Play Store → Storage & cache → Clear cache.
- Try the update again.
- If it still fails, come back and tap Clear storage.
- Then do the same cache only step for Google Play Services.
- Restart the phone before trying once more.
Nothing here touches the app you are trying to update. Clearing the store’s cache does not remove apps, purchases or app data. The only thing you lose is the store’s own search history and preferences.
Fix 2: Free up more space than you think you need
An update is not a patch on most phones. The new package is downloaded in full, unpacked, verified and only then swapped in — so for a short moment the old version, the download and the unpacked copy all exist at once.
That is why a 90 MB update can fail on a phone that reports 400 MB free. Aim for several times the update size, and check the real figure in Settings → Storage rather than trusting a cleaner app’s estimate. If there seems to be nothing left to delete, the space is usually hiding somewhere you have not looked.
Fix 3: Clear the update queue and the network restrictions
In the Play Store, open your profile picture → Manage apps & device → Manage, and cancel anything already downloading. One stalled job holds every other one behind it. That is the same queue behind the “Download pending” message.
Then check Settings → Network preferences → App download preference. If it says Over Wi-Fi only and you are on mobile data, the update will queue silently and never start. Android’s Data Saver does the same thing from the other direction.
Fix 4: Make sure the right account owns the app
If your phone has two Google accounts, the app was installed under one of them, and updates come through that same one. Switching the Play Store to the other account leaves the app visible but un-updatable.
- Tap your profile picture in the Play Store.
- Tap the arrow beside your email address to see the accounts on the phone.
- Switch between them and look at the app’s page under each.
- The account that shows Update rather than Install is the owner.
This also explains the region case: an app installed while your account’s country was set elsewhere may no longer be offered in your current country, and the store simply stops offering updates without explaining why.
Fix 5: The signature conflict — the one that needs a reinstall
Every Android app is signed. An update is only accepted if it is signed by the same key as the copy already installed. If it is not, Android refuses — usually as “App not installed” or error 505 — and no amount of cache clearing will change its mind.
You hit this when:
- the installed copy came from an APK site or a third-party store rather than the Play Store;
- a modified or “premium unlocked” build was installed over the original;
- the app was restored from a backup of a different build.
The only cure is to uninstall and install fresh from the Play Store.
Before you uninstall: anything the app stored only on the phone goes with it. Sign in to the app and check that your account, progress or chats are synced to a server first, and use the app’s own export or backup option if it has one. Apps that keep everything in an online account survive a reinstall untouched; apps that keep it locally do not.
Fix 6: When “Update” is greyed out or missing entirely
Three ordinary explanations, none of them a fault:
- The update is staged. Developers release in waves. Your phone may simply not be in the current wave, and the version number you saw announced is not available to you yet. Waiting a day or two is the fix.
- Your Android version is too old. The newest build requires a newer Android than your phone has, so the store quietly offers you nothing. The app’s Play Store page lists the requirement near the bottom.
- The device is managed. A work profile, school device or family-link setup can hand update control to an administrator. The app page then shows no button at all.
Fix 7: Turn automatic updates off, then update by hand
A useful trick when one app keeps failing while others are fine. Automatic updating retries in the background on its own schedule and can leave a half-finished job in place that blocks your manual attempt.
- Open the app’s page in the Play Store.
- Tap the three dots in the top right.
- Untick Enable auto update.
- Restart the phone, then open the page again and tap Update.
- Tick the box again once it succeeds.
Frequently asked questions
Does updating an app ever delete its data?
A normal update never does. Uninstalling does. That is the whole reason the signature-conflict case in fix 5 is worth treating carefully — it is the one route that forces a removal.
Is it safe to download the newer APK from a website instead?
It is how most people end up with the signature conflict in the first place, and a repackaged build can carry anything. If an app matters enough to update, it matters enough to update from the store that signed it.
Why do updates work on Wi-Fi but fail on mobile data?
Usually the download preference setting rather than the connection. Some carriers also interrupt large transfers, which shows up as a download that reaches 90% and restarts.
Can I go back to the previous version if the new one is worse?
Not through the Play Store — it only offers the current build. Turning off auto-update for apps you depend on is the realistic way to stay on a version that works for you.
The short version
Clear the Play Store cache, empty the update queue, make sure there is real free space, and confirm the right account owns the app. If the failure says “App not installed”, stop trying — that is a signature conflict, and only a clean reinstall from the Play Store will fix it.