Tap Download, watch the bar crawl, and then it quits: “App could not be downloaded due to an error. (921)” — even though you have storage free and other apps on the phone work fine online. Play Store Error 921 is a download-stage failure, not an install clash. The store’s download session gets interrupted or its account sync goes stale partway through, so Google’s servers stop the download and hand you this code instead of a reason. It is famously fussy about networks: the same download that fails again and again on one Wi-Fi network often sails through on mobile data. These 6 fixes for Play Store Error 921 start with the network, then work through the store’s own state, and they cover Android 10 through 14.

Quick Answer
For Play Store Error 921, first switch networks — turn Wi-Fi off and try the download on mobile data, or join a different Wi-Fi network. If it still fails, clear the Play Store cache under Settings → Apps → Google Play Store → Storage & cache, then clear its data too. Those two moves clear most 921 downloads.
In This Guide
- Fix 1: Switch Networks and Rejoin Wi-Fi Cleanly
- Fix 2: Clear the Play Store Cache, Then Its Data
- Fix 3: Clear Download Manager and Play Services Too
- Fix 4: Fix the Clock and Confirm You Actually Have Room
- Fix 5: Remove Your Google Account and Add It Back
- Fix 6: Roll Back the Play Store and Let It Update Itself
Fix 1: Switch Networks and Rejoin Wi-Fi Cleanly

Start here, not with cache-clearing: 921 is so often a network-session problem that this test alone settles the diagnosis. Works on another connection? The first network’s session was the blocker. Fails everywhere? The fault lives on the phone.
- Turn Wi-Fi off and try the download on mobile data. If it goes through, the Wi-Fi session was the problem. You can switch back to Wi-Fi afterwards for everything else.
- Still on Wi-Fi? Forget the network and rejoin it: Settings → Network & internet → Internet, tap the network, choose Forget, then connect again with the password fresh. Hotel, office and campus logins often expire mid-download.
- Turn off any VPN for the download. A VPN routing the store through another country can interrupt the download handshake, and 921 gives no hint the VPN is involved.
- Restart your router once if the Wi-Fi itself drops in and out, and keep the phone awake with the Play Store open during the retry. A phone that dozes mid-download can break the session on aggressive battery settings.
For a large game, test with a small app first — the point is diagnosis, not data use.
Fix 2: Clear the Play Store Cache, Then Its Data
When the network is innocent, the store’s own saved state is next. When its record of your downloads and account session goes stale, new downloads start broken and die with 921. Clearing in two stages — cache first, data second — shows which layer was at fault.
- Go to Settings → Apps → See all apps → Google Play Store → Storage & cache and tap Clear cache. Retry the download. If it works now, a corrupted cache entry was the whole story.
- If 921 returns, go back to the same screen and tap Clear storage as well. This wipes the store’s saved preferences on the phone — not your apps, not your purchases, not your account — and forces a clean session on the next open.
- Force-stop the Play Store from its App info screen, restart the phone, and open the Play Store before retrying. Let it settle for a few seconds on first open; a rushed retry can trip over the store still rebuilding its session.
- Try a small free app first rather than the big one that failed. If the small app downloads, the session is healthy again and the original app should follow.
Samsung (One UI): Settings → Apps → Google Play Store → Storage. Xiaomi (HyperOS): Settings → Apps → Manage apps → Google Play Store → Clear data.
Fix 3: Clear Download Manager and Play Services Too
The Play Store does not download alone: Download Manager runs the file transfer, and Google Play Services handles the account and licensing checks. Stale state in either one survives a store-only cache clear, so 921 keeps returning.
- Go to Settings → Apps → See all apps. Tap the three-dot menu and choose Show system apps, then open Download Manager. If it shows as disabled, tap Enable — a disabled Download Manager blocks every Play Store download, not just one.
- On its Storage & cache screen, tap Clear cache, and clear its data too if the error persists. This removes the stalled download entries, not your downloaded files.
- Repeat the cache-clear for Google Play services: Settings → Apps → See all apps → Google Play services → Storage & cache → Clear cache. Clear its storage only if 921 survives the cache step.
- Restart the phone, open the Play Store, and retry the original download on its own, with no other downloads running at the same time.
A useful tell: every app failing points at these system apps; one app failing while others download fine points at the account instead — skip to Fix 5 in that case.
Fix 4: Fix the Clock and Confirm You Actually Have Room
Two quiet settings can masquerade as a download error: a clock far from real time breaks the secure handshake with Google’s servers, and a phone down to its last megabytes fails downloads in confusing ways. Ruling both out takes two minutes.
- Go to Settings → System → Date & time and turn on Set time automatically and Set time zone automatically. If they were already on, toggle them off and back on once to force a fresh sync.
- Check storage under Settings → Storage. For the app you want, keep at least twice its size free — the download plus its install step need breathing room, and a phone showing only a few hundred megabytes free will stall downloads that look like they should fit.
- Clear the quick wins if space is tight: the Downloads folder, duplicate videos, and the caches of heavy apps under Settings → Apps → [app] → Storage & cache → Clear cache.
- Retry the download. If the clock was the culprit, the change is immediate — no restart needed for the time sync to take effect.
For 921, space and clock are checks to rule out, not the headline cause. If both check out, the account step below is where the real fix usually sits.
Fix 5: Remove Your Google Account and Add It Back

When cache-clearing and network-switching both fail, the account session itself is usually stale — 921 so often means “the store no longer trusts this session.” Removing and re-adding the account forces a fresh one; it takes minutes and touches nothing on the phone itself.
- Open Settings → Passwords & accounts, tap Google, open your account, and choose Remove account. Confirm. Your apps, photos and files stay where they are.
- Restart the phone. This matters — it clears any session the system was still holding for the removed account.
- Add the account back: Settings → Passwords & accounts → Add account → Google, and sign in with the same account you use for the Play Store. If you run two Google accounts on the phone, add the Play Store one first.
- Open the Play Store, let it load fully, and retry the download. If you use a second account for purchases, check that the Play Store is set to the right one — tap your profile icon in the store and confirm the account shown at the top.
A password or verification prompt during re-adding is normal — finish it on the phone rather than skipping it.
Fix 6: Roll Back the Play Store and Let It Update Itself
The final phone-side repair covers a Play Store whose own update misbehaves: it throws 921 across many apps at once, and cache-clearing cannot fix broken code. Rolling back to factory version and letting it update cleanly replaces it.
- From the Play Store’s App info page, open the three-dot menu and pick Uninstall updates. That strips the store’s updates while leaving the store itself and every installed app alone.
- Open the Play Store and 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.
- Check for a system update too: Settings → System → System update. Store and system updates sometimes travel together, and a pending system update can hold the store back.
- Restart the phone and retry the download. If 921 still blocks every app after all six fixes, back up your files and consider a factory reset under Settings → System → Reset options — but treat that as the last step, not the next one, since it wipes the phone.
Once a download lands, open the app and confirm it runs — a crash on launch is a separate fault, not another 921.
Related Guides
Video Guide: Fix Play Store Error 921
Video by VizTech — full credit to the creator.
Frequently Asked Questions
Why does switching to mobile data fix Error 921 when Wi-Fi does not?
Because 921 is a session problem, and the session rides on the connection. A Wi-Fi network with an expired login page, a captive portal, or a router that drops the store’s handshake breaks the download session, while mobile data starts a fresh one. If mobile data works, the phone and the account were never the problem.
Will clearing Play Store data delete my apps or my purchases?
No. Clearing the store’s cache and storage removes its saved preferences and download history on that phone. Your installed apps stay installed, your Google account stays signed in at the system level, and your purchase history lives on your Google account, not in the store app’s local data.
Error 921 keeps coming back for every app — what should I do first?
Work the list in order rather than repeating one step: confirm the network switch, clear the store and Download Manager state, then remove and re-add the account. A 921 that hits every app points at the session or the system apps, not at any single app’s listing, so the account step in Fix 5 is the one that most often ends it.
By Sameer Zehri | App Fix Guru Editor | Last updated: October 2026