How to Fix Google Play Store Error 103 on Android
What error 103 means
Error 103 is the Play Store's way of saying this app is not for this phone. You find an app you want — a new game, a banking app, a camera tool — tap Install, and a small pop-up appears: "the app could not be downloaded due to an error (103)." Retry does nothing. The download never starts, and the same message appears every time you try, whether it is a fresh download or an update to an app you already had.
In most cases the Play Store is telling the truth: your Android version is older than the app's minimum requirement, or the app needs hardware or a feature your phone does not have. Developers regularly raise their minimum Android version, and older phones quietly fall off the supported list. But error 103 is also famous for firing when nothing is actually incompatible. Stale cached compatibility data, a half-installed Play Store self-update, an incorrect system clock, or an uncertified device (rooted phones and some custom ROMs lose their Play Protect certification) can all make the store block downloads your phone would run perfectly fine. That is why this error deserves a troubleshooting pass before you write the app off.
The steps below start by verifying the compatibility facts — five minutes that tell you whether the block is real — and then move into the cache, update, and account resets that fix the false-positive cases. Most people have their answer within ten minutes.
Common causes
- Outdated Android version: the app requires a newer Android release than your phone is running, and the Play Store blocks the download.
- Genuine hardware incompatibility: the app needs a feature, chipset, or screen capability your phone does not have.
- Uncertified device: rooted phones and some custom ROMs fail Play Protect certification, and the store blocks downloads with 103.
- Stale cached compatibility data: old Play Store or Play Services cache makes the store apply a compatibility check that no longer matches your phone.
- Broken Play Store self-update or account token: a half-installed store update or stale Google account credential keeps the wrong device profile applied to your downloads.
How to fix error 103 — step by step
Work through these fixes in order. Step 1 tells you whether the block is real; steps 3 through 6 fix the false positives.
- Check whether the app is compatible with your phone. Error 103 means the Play Store thinks your device does not meet the app's requirements, so verify the facts first. Open the Play Store, tap your profile icon, then tap Play Protect > Certification and confirm your device shows as Certified — an uncertified device (rooted phones, some custom ROMs) gets 103 on apps it should run. Then open Settings > About phone and note your Android version, and compare it with the app's listed requirements on its Play Store page under App info > About this app.
- Update Android to the latest available version. Many apps drop support for old Android releases, and error 103 is how the Play Store tells you your OS is too old. Open Settings > System > System update (on Samsung: Settings > Software update > Download and install) and let the phone check for updates. Install anything it finds and restart. If no update is offered, your phone has hit the end of manufacturer support for its Android version.
- Clear the Play Store and Google Play Services cache and data. Sometimes error 103 is not real incompatibility at all — stale cached compatibility info makes the store block a download your phone can actually run. Go to Settings > Apps > See all apps, open Google Play Store, then tap Storage & cache and hit Clear cache followed by Clear storage (or Clear data) and confirm. Go back, find Google Play Services (tap the three-dot menu > Show system to see it), and clear its cache and data the same way. Restart the phone and retry the download.
- Uninstall updates to the Play Store app. In Settings > Apps > See all apps, open Google Play Store and tap the three-dot menu in the top-right corner, then Uninstall updates. This rolls the store back to the factory version that shipped with your phone, undoing a half-installed self-update that may have broken its compatibility checks. Open the Play Store — it will quietly reinstall a fresh update on its own — then wait a few minutes and retry your download.
- Set the date and time to automatic. Go to Settings > System > Date & time and turn on Set time automatically and Set time zone automatically (both toggles). An incorrect clock breaks the Play Store's certificate and signature checks, which can surface as error 103 during download. If both were already on, try turning them off, setting the time manually, restarting the phone, and switching them back on. Then reopen the Play Store and try the download again.
- Remove your Google account and add it back. If the error keeps firing, a stale account token can keep the store applying the wrong device profile to your downloads. Go to Settings > Passwords & accounts, tap your Google account, then Remove account. Restart the phone, go back to Settings > Passwords & accounts, tap Add account > Google, and sign in again. Open the Play Store and retry the download.
Did this fix it? Quick checklist
- The app's Play Store page no longer shows a compatibility warning
- The download starts and completes without the 103 pop-up
- Play Store > profile > Play Protect shows the device as Certified
- The fix holds after a phone restart and an Android update check
If error 103 still appears after all six steps, the block is probably real: your phone genuinely does not meet the app's minimum Android version or hardware requirements. Check the app's Play Store page for the listed Android requirement under App info > About this app, and as a last resort look for a device that meets it — a factory reset will not make an incompatible app compatible.
Frequently asked questions
What does Google Play Store error 103 mean?
Error 103 means the Play Store believes the app you are trying to download is not compatible with your device — a pop-up says the app could not be downloaded due to an error (103). In most cases your Android version is too old for the app, or the app's minimum requirements exceed your phone's specs. Sometimes it is a false flag caused by stale Play Store cache, a half-installed Play Store update, or an uncertified device, which is why the cache-clearing steps fix it even on phones that look compatible.
Will error 103 fix itself if I just wait?
Occasionally. Error 103 can come from a server-side app-signature issue at Google, and the Play Store does correct itself once Google pushes an updated signature. But most cases are local — an old Android version, cached compatibility data, or an uncertified device — and those never clear on their own. Work through the steps above rather than waiting; they take about ten minutes.
Why do I get error 103 only on this phone and not my other device?
Because error 103 is device-specific. Your other phone probably runs a newer Android version, has a newer chipset the app requires, or is Play Protect certified while this one is not (rooted phones and many custom ROMs lose certification). Check the app's minimum Android version on its Play Store page and compare it against Settings > About phone on the failing device — the gap is usually obvious.
Can I sideload the app to bypass error 103?
Only download apps from sources you trust, but technically yes — if the incompatibility is a false flag from cached data, sideloading the APK can work. If the incompatibility is real, though (the app genuinely needs a newer Android version or hardware your phone lacks), the sideloaded app will crash or refuse to install. It is safer to clear the Play Store cache, update Android, and let the store serve you the right package than to install a mismatched APK from an unknown site.