How to Fix Google Play Store Error 505
What error 505 means
Error 505 appears when the Google Play Store can’t install an app because of a duplicate permission conflict. On Android, certain powerful permissions can only be claimed by one app on the device. If the app you’re installing declares one of those permissions and another app already holds it, Android rejects the install with error 505.
This crops up most often with sideloaded or modified apps: you install an APK from outside the Play Store, then try to install the Play Store version (or the other way around), and the two builds declare the same custom permission with different signatures. Apps built on Adobe AIR were the classic historical trigger, but any pair of same-permission, differently-signed apps can cause it.
The fix is logical rather than technical: remove the conflict. Once only one claimant for the permission remains — or you install a build signed consistently with what’s already there — the install proceeds.
Common causes
- Duplicate custom permission: two apps declaring the same signature-level permission.
- Sideloaded vs. Play Store builds: the same app from two sources, signed with different keys.
- Leftover data from an uninstalled app: remnants still registering the permission after removal.
- Corrupted Play Store cache: the store misjudging the conflict state.
- Outdated Android version: older releases handle permission conflicts less gracefully.
How to fix error 505 — step by step
The fix is logical: remove the conflict. Work through these steps in order.
- Clear the Play Store’s cache and data. Open Settings > Apps > See all apps > Google Play Store > Storage & cache. Tap Clear cache, then Clear storage. Clear the cache for Google Play Services the same way. Retry the install — sometimes the “conflict” is just the store’s stale view of what’s installed.
- Find and uninstall the conflicting app. Think about which installed app is related — the same app from another source, a modified version, or an older sideload. Go to Settings > Apps > See all apps, tap the conflicting app, then Uninstall. Then install your desired version fresh from the Play Store.
- Check for duplicate or disabled copies. In Settings > Apps > See all apps, tap the three-dot menu and choose Show system, then look for duplicate or disabled versions of the app. Uninstall the extras so only one copy exists — hidden duplicates are a sneaky cause of 505.
- Install a consistently signed APK. If you must sideload, get the APK from the same source and signer as any related installed app — matching signatures avoid the conflict entirely. First enable Settings > Apps > Special app access > Install unknown apps for your browser or file manager, then install.
- Update Android. Go to Settings > System > System update > Check for update and install anything available. Newer Android versions resolve some permission conflicts more cleanly. Restart the phone after updating, then retry the install.
Did this fix it? Quick checklist
- Only one version of the conflicting app is installed
- Play Store cache and data have been cleared
- The install completes without error 505
- The app launches and requests its permissions normally
If you can’t find the conflicting app, the culprit may be a disabled system app still holding the permission — check the full app list with system apps shown. As a last resort, back up your phone and factory reset, then install the Play Store version first.
Frequently asked questions
What is error 505 on the Play Store?
An install blocked by a duplicate permission: two apps claim the same signature-level permission, so Android refuses the new install until the conflict is removed.
Why does error 505 happen with modified APKs?
Modified builds are signed with different keys than the original app but declare the same custom permissions — exactly the conflict Android rejects. Installing the official build, or removing the other copy first, resolves it.
Will I lose data uninstalling the conflicting app?
The uninstalled app’s local data goes with it unless the app syncs to an account or cloud backup. Sync or back up first if the data matters to you.
Can error 505 mean my phone is hacked?
No. It’s a developer packaging conflict — two apps declaring the same permission — not an intrusion. It looks technical, but the cause is mundane.