You're halfway through updating your apps when the Play Store stops and delivers its verdict: "Could not be downloaded due to an error (927)." No explanation, no suggested fix — and every download and update behind it stops cold too.
Here's the part Google never puts on screen: 927 is one of its oldest download codes, and it almost always means the store was interrupted mid-job. The classic trigger is the Play Store updating itself at the moment you asked it to download something. The others are a cache left broken by an interrupted download, free storage dropping under roughly 1 GB, or a Google account token gone stale. Notice what's not on that list: Google's servers. This is a client-side error — the breakage lives on your phone — which means you can fix it yourself. Covers Android 10 through 14.
Quick Answer: Do nothing first — seriously. Error 927 most often appears while the Play Store is updating itself, so wait 10–15 minutes and retry. Still there? Clear the store's cache at Settings → Apps → Google Play Store → Storage & cache → Clear cache, and check Settings → Storage: under about 1 GB free, downloads fail with 927 instead of an honest storage warning.
Fix 1: Wait Out the Play Store's Self-Update
The store updates itself silently in the background, and during that window it cannot serve downloads — requests bounce back as 927. Fighting this with settings changes is wasted effort, because the "fault" fixes itself:
- Close the Play Store and wait 10–15 minutes. The self-update usually completes quietly in the background.
- Reopen the Play Store and retry the download. If the update has finished, the error is simply gone.
- To check: open the Play Store → profile icon → Settings → About and tap Update Play Store. If it says the store is up to date, the self-update is done and 927 needs another explanation — move to Fix 2.
- One more clue: if other apps are sitting in "Waiting" or "Pending" in the downloads list, the store's pipeline is still busy. Give it more time before retrying.
Fix 2: Clear the Play Store's Cache — Then Its Data
If 927 appeared right after a download failed or was interrupted, suspect the cache: the store keeps partial download files there, and on the next attempt it tries to resume from a broken one and throws 927 instead.
- Go to Settings → Apps → See all apps and tap Google Play Store. (Not visible? Tap the ⋮ menu → Show system apps.)
- Tap Storage & cache → Clear cache.
- Go back, tap Force stop → OK, then reopen the Play Store and retry the download.
- Error persists? Repeat the path and tap Clear data / Clear storage too. The store resets to defaults — you'll re-accept its terms on the next launch, but your apps and purchases are untouched.
Brand paths: Samsung (One UI) — Settings → Apps → Google Play Store → Storage → Clear cache. Xiaomi (HyperOS) — Settings → Apps → Manage apps → Google Play Store → Storage → Clear cache. Cache alone resolves most cache-related 927s; only escalate to Clear data if it didn't.
Fix 3: Clear the Download Team's Caches
The store doesn't download alone. Google Play Services handles authentication and the download machinery, Google Services Framework keeps the phone's identity with Google, and Download Manager does the fetching — corrupted data in any of them surfaces as the same 927.
- Go to Settings → Apps → See all apps, tap the ⋮ menu → Show system apps.
- Open Google Play Services → Storage & cache → Clear cache.
- Repeat for Google Services Framework and Download Manager if they appear in the list.
- Force-stop Google Play Services, restart the phone, then retry the download.
One warning worth heeding: on Google Play Services, tap Clear cache only. Avoid Clear data / Manage space → Clear all data there unless a guide specifically walks you through it — Play Services data touches many Google apps at once. The restart afterwards lets every dependent service reload cleanly.
Fix 4: Make Room — the 1 GB Rule
Google's own guidance flags devices with less than 1 GB of free space as prone to download failures — and a phone tight on space often surfaces Error 927 instead of a clear "storage full" message, because the store can't finish writing its temporary install files.
- Go to Settings → Storage and check the available space. Under 1 GB, freeing space is likely required, not optional.
- Clear caches in bulk: Settings → Storage → Cached data / Other apps (paths vary — Samsung: Settings → Battery and device care → Storage; Xiaomi: Settings → About phone → Storage, or the Security app → Cleaner).
- Delete the big things: the Files app → Clean (Pixel) or My Files → Analyze storage (Samsung) highlights the largest space hogs — large videos and duplicate downloads first.
- Move photos and videos to Google Photos backup and use its Free up space to remove the device copies, and uninstall apps you no longer use.
- Aim for at least 2 GB free before retrying a large download — the store needs headroom beyond the app's own size for its temporary files.
Fix 5: Refresh Your Google Account
Every download runs against your account's authentication tokens, and a stale token stalls the pipeline with 927. Removing and re-adding the account mints fresh ones:
- Go to Settings → Passwords & accounts (Samsung: Settings → Accounts and backup → Manage accounts; Xiaomi: Settings → Accounts & sync).
- Tap your Google account → Remove account and confirm. This signs the account out of the phone only — your data stays on Google's servers.
- Restart the phone.
- Return to Settings → Passwords & accounts → Add account → Google and sign in with the same account.
- Open the Play Store and retry the download.
Know your Google password before you remove the account — you'll need it to sign back in. If this phone is your only trusted device, make sure a recovery email or phone number is set on the account first.
Fix 6: The Full Refresh — Force Stop, Stable Network, System Update
When the targeted fixes haven't cleared 927, refresh the whole stack at once. Interrupted downloads are the classic trigger for this error, so connection stability matters as much as any setting here:
- Force-stop the Play Store: Settings → Apps → Google Play Store → Force stop → OK.
- Change the road: switch between Wi-Fi and mobile data and retry on whichever is steadier.
- Restart the phone: hold Power (Samsung: Side + Volume Down) and tap Restart.
- Check for a system update: Settings → System → System update (Samsung: Settings → Software update → Download and install; Xiaomi: Settings → About phone → HyperOS version). Play Store and framework bugs are patched in OS updates.
- Open the Play Store, force-check its own update (profile icon → Settings → About → Update Play Store), then retry the download.
Brand note: on Xiaomi (HyperOS), the Play Store data path is Settings → Apps → Manage apps → Google Play Store → Clear data, and system updates live under About phone → HyperOS version.
If 927 Survives All Six Fixes
Then widen the net, in this order. Try a genuinely different network — some Wi-Fi networks (office, school, captive portals that demand a sign-in page) interfere with Play Store downloads; mobile data settles it. Reset app preferences at Settings → System → Reset options → Reset app preferences, which restores all app permissions and defaults without deleting data. Check the clock: Settings → System → Date & time → Set time automatically — a wrong clock can break the Play Store's secure connection and surface odd error codes, 927 among them. Reset network settings (Settings → System → Reset options → Reset Wi-Fi, mobile & Bluetooth; Samsung: Settings → General management → Reset → Reset network settings) — but know it erases saved Wi-Fi passwords and Bluetooth pairings. And if 927 persists across accounts and networks after all of that, it's time for the official channel: Play Store → profile icon → Help & feedback. Covers Android 10 through 14.
Watch: Play Store Error 927 Fixed Step by Step
Prefer a walkthrough? This video covers fixing Google Play Store error 927 step by step:
Video by Howtosolveit — full credit to the creator.
Related Guides:
927, in Plain Terms
What actually causes Play Store Error 927?
An interruption. Most often the Play Store was updating itself when you asked for a download; otherwise, a cache left broken by a failed download, free storage under about 1 GB, or a stale account token. It's generated on your phone, not by Google's servers — which is why the fixes above are all local.
Will clearing the Play Store's data delete my apps?
No. Clear cache and Clear data on the Google Play Store only reset the store app itself. Your installed apps, purchases, and download history are tied to your Google account and stay exactly as they are — at most, you'll re-accept the store's terms on the next launch.
Why does Error 927 keep coming back?
Because the trigger underneath it is still alive: an unstable connection that keeps interrupting downloads (retry on stable Wi-Fi — Fix 6), storage that keeps sinking under 1 GB (Fix 4), or an outdated Play Store build (check Settings → About → Update Play Store). Fix the trigger and the code stops returning.
By Sameer Zehri | App Fix Guru Editor | Last updated: October 2026
