Error code 505 on Android phones is a Google Play Store installation error that appears when an app fails to install or update. The fix usually involves clearing the Play Store cache, removing an outdated app update, or checking for a system update, and this article walks through each step in order of likelihood.
What Error 505 Actually Means
Android error 505 is a generic installation failure code returned by the Play Store. It typically reads “Can’t install app” or “Error retrieving information from server. [RPC:S-5:AEC-0]” and is most commonly triggered when the app you are trying to install shares a signature or permission conflict with an existing app on your device. It is not a virus or a sign of hardware failure, and it rarely means your phone is broken.
The error is tied to the Android package installer, not to the app itself. That means the same app may install fine on another phone, and the problem is specific to the device state. Common triggers include a corrupted Play Store cache, a pending Android system update, or an old version of the Play Store app that no longer matches the app’s target SDK.
Why It Happens on Some Phones and Not Others
Android fragmentation is the root cause. App developers target a specific Android version (SDK level), and when your phone runs an older version of Android than the app requires, the package installer can throw a 505 error instead of a clearer “incompatible” message. For example, an app built for Android 12 may fail on a phone still running Android 9 with this generic code.
Another common cause is a leftover data conflict. If you previously installed the app from a different source (like an APK file or a different Google account), the signature on the existing installation does not match the Play Store version, and the installer refuses to overwrite it. This is a security measure, but it surfaces as error 505.
Step-by-Step Fixes to Try First
Work through these in order. Each fix takes under two minutes and does not erase personal data.
- Restart the phone. This clears temporary installer locks and is the simplest fix. Hold the power button, tap Restart, and try the install again.
- Clear the Play Store cache and data. Go to Settings > Apps > Google Play Store > Storage, then tap Clear Cache followed by Clear Data. You will need to sign into the Play Store again, but your apps and purchases remain.
- Remove the app’s old data. If the failing app is already installed, go to Settings > Apps > [app name] > Storage and tap Clear Data. Then uninstall the app completely and reinstall from the Play Store.
- Check for a system update. Go to Settings > System > System update (or About phone > Software update on some brands). Install any pending update, restart, and retry.
- Update the Play Store itself. Open the Play Store, tap your profile icon, go to Settings > About, and check for a Play Store update. If none is available, the store updates itself in the background.
When the Basic Fixes Don’t Work
If the error persists, the problem is likely a deeper conflict. Try these next:
- Remove and re-add your Google account. Go to Settings > Accounts > Google, tap your account, choose Remove account, then add it back. This resets the account-level permissions that the Play Store uses. Your apps and data stay on the phone, but you may need to re-enter passwords for some services.
- Check for multiple user profiles. If you use a work profile or a second user on the same phone, log into that profile and try installing the app there. Sometimes the error is isolated to one profile’s data.
- Boot into Safe Mode. Press and hold the power button, then long-press Power off and confirm Safe Mode. In Safe Mode, third-party apps are disabled. If the app installs successfully there, a background app is interfering. Restart normally and uninstall recently added apps.
- Reset app preferences. Go to Settings > Apps > three-dot menu > Reset app preferences. This restores default permissions and notification settings without deleting any app data.
What to Do If the App Still Won’t Install
If you have tried all the above and the error remains, the issue may be with the app itself or with your phone’s storage. Check available storage first: go to Settings > Storage and make sure you have at least 500 MB free, as some apps need extra space for temporary files during installation. If storage is fine, contact the app developer through the Play Store listing’s Contact developer link. Include the error code and your phone model and Android version. Developers can see server-side logs and may push a fix.
Another option is to wait. Play Store errors like 505 sometimes resolve after a few hours when the developer updates the app or Google updates the store’s compatibility checks. You can also try installing the app from the web version of the Play Store (play.google.com) on a computer, which sometimes bypasses a corrupted local store state.
Preventing Error 505 in the Future
Most future occurrences are avoidable with a few habits:
- Keep Android updated. System updates include the package installer fixes that address exactly these errors.
- Install apps only from the Play Store. Sideloaded APKs can leave behind signature mismatches that trigger 505 later.
- Don’t use “clear data” on the Play Store unless needed. It resets your store preferences and can sometimes make the error worse if you have many apps installed.
- Use the same Google account for all installs. Switching accounts on a phone can cause permission conflicts with previously installed apps.
Frequently Asked Questions
Will clearing Play Store data delete my apps?
No. Clearing the Play Store’s data only resets the store’s own settings, such as your search history and notification preferences. Your installed apps and their data remain untouched. You will need to sign into the Play Store again, but that is a minor inconvenience.
Is error 505 the same as error 495 or 504?
No. Error 495 is a download error, 504 is a server timeout, and 505 is an installation conflict. They have different causes and fixes, though clearing the Play Store cache is a common first step for all three. If you see 505, focus on signature and compatibility issues rather than network problems.
Can I install the app as an APK to bypass error 505?
You can, but it is not recommended. Downloading an APK from an unofficial source risks malware, and the APK may not match the Play Store’s signature, which can cause the same error later when you try to update. If you must sideload, use the developer’s official website or a trusted source, and uninstall the Play Store version first.
Why does error 505 happen on a brand-new phone?
On a new phone, the most likely cause is an outdated system version out of the box. Many budget phones ship with an older Android version and a pending system update. Install the update first, then try the app again. Another possibility is that the app was preloaded by the manufacturer with a different signature, so the Play Store version cannot overwrite it.
Does a factory reset fix error 505?
Usually, yes, because it removes all app conflicts and resets the package installer. But it also erases all your data, so it should be a last resort. Back up your photos, contacts, and files first. After the reset, sign in with the same Google account and try the install before restoring any backups, to confirm the error is gone.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Show User Library in macOS High Sierra & Sierra
- Device Manager Shortcut: Windows 10 Desktop
- How to Remove Forgotten Passcode from iPhone
- Fix Slow Wi-Fi Problem iPhone X: 9 Steps
- How to Check if a Candidate Accepts Crypto Donations
- How to Listen to Deleted Voicemails on iPhone