You tap Update, the download finishes, and then the Play Store stops dead with “Can’t install app. Try again, and if the problem continues, get help troubleshooting. (Error code: -505)”. The download itself worked, so a weak signal is not the story here. Play Store Error 505 is a permission clash: two apps on your phone are asking Android for the same custom permission, and Android refuses to install the second one until the clash is gone. It shows up most often when you update an app you already have — YouTube, WhatsApp, Facebook and Messenger are the usual names — because the new version’s permission list collides with an older copy still sitting on the phone. These 6 fixes for Play Store Error 505 hunt down that clash first, and they cover Android 10 through 14.

Quick Answer
Play Store Error 505 means two apps want the same permission, so Android blocks the install. First, uninstall the older or duplicate copy of the app — including any copy installed for another user or work profile — then clear the Play Store cache and try the install again. That single step clears the clash behind most 505 errors.
In This Guide
- Fix 1: Remove the App That Is Clashing With the Update
- Fix 2: Clear the Play Store, Play Services and Download Manager Data
- Fix 3: Uninstall the App’s Updates and Reinstall It Fresh
- Fix 4: Roll Back the Play Store and Refresh Play Services
- Fix 5: Take the SD Card Out of the Equation
- Fix 6: Refresh Your Google Account and Reset App Preferences
Fix 1: Remove the App That Is Clashing With the Update
With 505, clearing caches first is putting the cart before the horse: Android is saying “I already gave this permission to another app.” Until that other claimant is gone, cache-clearing changes nothing. The clash is usually a second copy of the same app, or a lookalike — duplicate messengers, two VPN apps, or an old beta build left beside the release build.
- Go to Settings → Apps → See all apps and search for the app that failed. If you see it twice — once active and once disabled, or a beta and a release build — uninstall the older or disabled one first.
- If the app was sideloaded once as an APK and later installed from the Play Store, remove the sideloaded copy completely. A leftover APK install signed with a different key blocks the Play Store version from taking its place.
- Check hiding places too: a second user profile (Settings → System → Multiple users), a work profile, or Samsung’s Secure Folder — each counts as a separate install.
- Uninstall for every user where your phone offers that choice. A plain uninstall from your own home screen sometimes leaves the other profile’s copy in place, and the clash survives.
- Restart the phone, open the Play Store, and install the app fresh. If the same 505 appears for a different app too, note which apps share a theme — two banking apps or two launchers are the classic pairs — and remove the one you use less.
No duplicate in sight? Move on to Fix 2 — a half-removed app can leave residue Android still holds, and the cache steps clear it.
Fix 2: Clear the Play Store, Play Services and Download Manager Data

Once the clashing app is gone, stale Play Store state can still replay the old refusal. Clearing cache and data for all three system apps forces a re-check against the phone’s real permission list.
- Go to Settings → Apps → See all apps → Google Play Store → Storage & cache. Tap Clear cache, then Clear storage. Clearing storage signs you out of the store’s saved preferences only — your installed apps and purchases stay put.
- Repeat for Google Play services (cache first, storage only if the error repeats), then find Download Manager — tap the three-dot menu and Show system apps if it is hidden — and clear its cache.
- Force-stop the Play Store from its App info screen, restart the phone, and open the Play Store again before retrying the install.
- If the app still throws 505, also clear the cache of the failing app itself under Settings → Apps → [app] → Storage & cache → Clear cache. Do not clear its storage yet — that deletes its local data, and you only need it if the clean reinstall in Fix 3 also fails.
On Xiaomi (HyperOS): Settings → Apps → Manage apps → Google Play Store → Clear data. Pixel phones use the path written above.
Fix 3: Uninstall the App’s Updates and Reinstall It Fresh
When 505 strikes on an update, the new version’s permission set no longer matches the old one underneath it. Stripping the app back to factory version, or removing it entirely and installing clean, breaks that mismatch.
- Go to Settings → Apps → [the failing app]. If it is a system app such as YouTube, tap the three-dot menu and choose Uninstall updates, then restart the phone.
- For a regular app, tap Uninstall instead, and confirm it is gone from the app drawer before continuing.
- Open the Play Store, search for the app, and install it as if it were new. Do not restore it from a backup or re-sideload an old APK at this stage; either one can reintroduce the same permission set that caused the clash.
- Open the app once and sign in again if it asks. If the fresh install lands without 505, the old version’s permission record was the problem, and your later updates should behave normally.
If you sideload apps, keep one source per app — Play Store or APK, not both. Mixed signatures invite 505 back.
Fix 4: Roll Back the Play Store and Refresh Play Services

Sometimes the broken piece is the store itself: a Play Store update that mishandles permission checks throws 505 for app after app. Rolling it back to factory version and letting it update itself cleanly resets that behaviour.
- Go to Settings → Apps → Google Play Store, tap the three-dot menu, and choose Uninstall updates. Confirm — this removes Play Store updates only, not the store and not your apps.
- Open the Play Store. It will look older for a moment; leave it connected for a few minutes while it updates itself in the background.
- To check manually, tap your profile icon → Settings → About → Update Play Store and let it confirm the version.
- While you are there, check the system side: go to Settings → System → System update and install any pending update, since store and system permission handling sometimes change together. Then retry the failing app.
If 505 now hits only one app, the fault is back to that app’s own record — reinstall it clean via Fix 3.
Fix 5: Take the SD Card Out of the Equation
An SD card adds a second storage location with its own permission rules, and a failing or read-only card can turn a clean install into a 505. This step rules out the whole storage side at once.
- Go to Settings → Storage and tap Unmount SD card (on Samsung: Settings → Battery and device care → Storage → Advanced → SD card → Unmount). Wait for the confirmation before touching the card.
- If your phone lets you remove the card, take it out, then retry the install with internal storage only. If the app installs cleanly, the card — or an app moved to it — was part of the clash.
- Reinsert and remount the card. Move any app living on it back to internal storage first, then retry its updates.
- Also check raw free space under Settings → Storage while you are there. Aim for at least 1 GB free: a phone squeezed to its last megabytes can fail installs with misleading codes, and freeing space removes that confusion.
No SD card? Skip this fix — it does not apply to you.
Fix 6: Refresh Your Google Account and Reset App Preferences
Before any factory reset, try a clean account and preference slate: a stale token can keep the store replaying an old install decision. Neither step deletes your apps, photos or files.
- Go to Settings → Passwords & accounts (on older phones: Accounts) → Google → your account → Remove account. Restart the phone, then add the same account back under Settings → Passwords & accounts → Add account → Google.
- Go to Settings → Apps → See all apps, tap the three-dot menu, and choose Reset app preferences. This re-enables disabled system apps and restores defaults; it deletes no app data.
- Check the clock while you are in Settings: go to Settings → System → Date & time and make sure Set time automatically is on. A clock far off real time breaks the store’s server handshake and can dress itself up as an install error.
- Open the Play Store and try the app once more. If 505 still blocks every app, back up and consider a factory reset — only after the five fixes above, since it wipes the phone.
After a successful install, open the app and confirm it runs — a crash on launch is a different fault, not another 505.
Related Guides
Video Guide: Fix Play Store Error 505
Video by CardChronicles — full credit to the creator.
Frequently Asked Questions
What exactly causes Play Store Error 505?
Two apps declaring the same custom permission. Android gives that permission to the first app installed, and when a second app asks for it, the install is refused with 505. The usual pair is a duplicate copy of the same app, or two similar apps — two messengers, two VPNs, two launchers — whose permission lists overlap.
I only have one copy of the app — why do I still get 505?
The other copy may be hiding: a second user profile, a work profile, Secure Folder on Samsung, or a disabled build that was never fully removed. Uninstalling from your home screen alone sometimes leaves those copies in place. Check every profile and choose “uninstall for all users” where your phone offers it.
Will clearing Play Store data delete my installed apps or purchases?
No. Clearing the Play Store’s cache and storage removes the store’s saved preferences and search history on that phone. Your installed apps, your Google account and your purchase history stay untouched, and the store rebuilds its preferences the next time you open it.
By Sameer Zehri | App Fix Guru Editor | Last updated: October 2026