Android 'Couldn't install' error 505: the Play Store fix that works

You tap 'Update' in the Play Store, it downloads fine, then pops 'Couldn't install — Error 505' right before the progress bar fills. This hits most often when updating Google Maps, Chrome, or banking apps on Android 11 through 14 — especially after a system update or switching from a custom ROM back to stock. I've seen it on Samsung Galaxy S22s, Pixel 7s, and OnePlus 10s. The app's APK downloads to your device, but the Android package manager (the system component that actually installs the app) can't reconcile the new package's signature with the old one.

Root cause: a stale cached package

What's actually happening here is the Play Store downloads the updated APK, hands it to the PackageManager service, and that service tries to compare the new app's certificate with the one already installed. Error 505 fires when the cached version of the old APK in /data/app/ or the Dalvik cache has a corrupted or mismatched signature entry. This isn't a storage issue — it's a package verification failure.

The reason clearing the Play Store's data alone doesn't always fix it: the stale signature info is stored in the Google Play Services cache and the system's package cache separately. You have to kill both.

The fix: step-by-step

1. Clear the Play Store and Play Services caches
   Go to Settings > Apps > Google Play Store > Storage & cache. Tap Clear cache (not storage — you lose fewer settings). Do the same for Google Play Services under the same path. The reason step 1 matters: clearing cache removes only temporary files, not your account data, which keeps you from having to re-sign in.
2. Uninstall Play Store updates
   Still in the Play Store's app info page, tap the three-dot menu in the top right, then Uninstall updates. This rolls the Play Store back to the factory version. It'll auto-update later, but doing this clears any corrupted updater binaries. On Samsung devices, this also removes the Galaxy Store's interference layer.
3. Delete the app's cached data manually
   Go to Settings > Apps > (the failing app) > Storage & cache. Tap Clear storage — this deletes the app's local data and cache. This isn't always necessary, but if the error persists after steps 1–2, the old app's cached package verifier data is the culprit. You'll have to sign back into the app after this.
4. Reboot into safe mode and clear the system cache partition
   Boot into safe mode (on most devices: hold Power, then long-press 'Restart' on the prompt). While in safe mode, third-party apps don't load, so the PackageManager can isolate the system cache. Go to Settings > Storage > Apps and clear cache again for the Play Store and Google Play Services. Then reboot normally. This step forces Android to rebuild the package cache from scratch.
5. Retry the install
   Open the Play Store, wait 30 seconds for it to re-initialize, then install the app again. It'll likely go through now because the signature verification cache is clean.

If error 505 still shows up

Two things left to try:

• Remove and re-add your Google account
  In Settings > Accounts > Google, tap your account, then Remove account. Reboot, then add it back. This resets the sync tokens the Play Store uses for app license verification. You'll lose saved Wi-Fi passwords synced with Google — so note those first if you're not using a password manager.
• Check for parallel space or dual app features
  Samsung's Dual Messenger, Xiaomi's Dual Apps, or app cloners create a second app profile that can conflict with the original app's signature cache. Disable all cloned instances of the failing app from Settings > Advanced features > Dual Messenger (or the equivalent on your device), then retry.

If neither works, the app itself might have a broken build on the Play Store. Check APKMirror or the app's official site for a sideloadable APK. But 9 times out of 10, the five-step cache clear above kills error 505 dead.