The store opens without a fight. You search for the app you need, tap its listing — and you're looking at your home screen again. Or the download bar climbs to 80%, the whole store vanishes, and the download dies with it. A Play Store that crashes mid-task is a different problem from one that won't open at all, and it needs a different order of attack.
Here's why. Opening the store is the easy part; the heavy jobs start afterwards. App pages are rendered by Android System WebView, downloads and installs are run by Google Play Services, and every install needs spare storage to unpack into. A fault in any of those only shows itself when that particular job begins — which is why the store can look healthy for ten seconds and then fold. The six fixes below follow the work, not the launch.
Quick Answer: For a store that opens but crashes while you use it, start with the components that do the work: update Android System WebView and the Play Store itself, then check Settings → Storage — keep at least 1–2 GB free or installs will keep dying mid-download. Next, refresh your Google account sync and clear the Google Play Services cache. Covers Android 10 through 14.
Fix 1: Update the Play Store and Android System WebView
When the crash happens as an app page loads — or the moment you tap Install — suspect the renderer first. Much of what the store displays is drawn by WebView, and a buggy WebView update is one of the most common causes of sudden, mid-use crashes across Google apps.
- Open the Play Store → profile icon → Settings → About and tap Update Play Store to pull in any newer store build.
- Search the Play Store for Android System WebView. If an Update is offered, install it and repeat whatever crashed.
- Already current, or updating changed nothing? Open Settings → Apps → Android System WebView → ⋮ menu → Uninstall updates, restart the phone, and test again — rolling back a bad WebView build is a well-trodden fix. You can let it update again afterwards; the corrected build usually follows quickly.
On some Xiaomi and Oppo phones there is no separate WebView app — the manufacturer's own browser component does the job, so check for updates to the stock browser instead.
Fix 2: Give Installs Room to Land
A download is not one file arriving; it's a package that downloads, unpacks, and installs — three stages that all need working space at once. On a nearly full phone the store starts the job, runs out of room halfway through, and dies without ever saying the word "storage."
- Open Settings → Storage and look at the free figure. If it's under 1–2 GB, treat storage as the prime suspect.
- Free space where it's cheapest: unused apps (Play Store → profile icon → Manage apps & device → Manage), the Downloads folder, and large videos you can move to cloud backup.
- Restart the phone, then retry the exact download that crashed. If it now completes, the crash was a space failure wearing a disguise.
Fix 3: Refresh the Google Account Session the Store Works Under
Mid-browsing, the store is constantly checking your library, licences, and payment methods against your Google account. A sign-in session that has quietly gone stale can make the store fold the moment one of those checks fails — often while opening your library or starting a purchase.
- Go to Settings → Passwords & accounts → Google (Samsung: Accounts and backup → Manage accounts), tap your account, then Account sync, and run Sync now from the ⋮ menu.
- Test the store on the screen that used to crash it.
- Still folding? Remove the account from the same screen, restart the phone, then add the account back. Know your password before you start — your purchases, mail, and contacts live in the cloud and return with the sign-in; nothing is deleted.
Fix 4: Clear Google Play Services' Cache
Play Services is the engine room: it handles authentication, the download machinery, and half of what the store does on screen. Corrupted data there crashes the store even when the store app itself is perfectly fine — which is exactly the mid-task pattern.
- Go to Settings → Apps and find Google Play Services. On some phones you need the ⋮ menu → Show system apps first.
- Tap Force stop, then Storage → Clear cache, and test the store.
- Only if that fails, go back and tap Clear data (or Manage space → Clear all data), then restart. The first launch afterwards may crawl — Play Services is rebuilding what it needs.
Clearing Play Services data is safe for your apps, photos, and files, but it resets some Google settings: a few apps may ask you to sign in again, and Google Wallet cards may need re-adding. That's why the cache goes first, always.
Fix 5: Roll Back a Store Update That Started the Crashes
Use timing as evidence. The Play Store updates itself silently, and if the mid-use crashes began within a day or so of one of those updates, the new build is the likely fault — no cache clear repairs a buggy version.
- Open Settings → Apps → Google Play Store.
- Tap the three-dot ⋮ menu (top right) and choose Uninstall updates. On Samsung (One UI), the option sometimes sits directly on the app-info screen.
- Confirm, restart the phone, and use the store. It will re-update itself in the background over the next few minutes — give it that time before judging.
Don't go hunting for a Play Store APK to sideload instead; the store's own self-update is cleaner and safer than a file from the internet.
Fix 6: Lift the Battery and Data Restrictions That Kill It Mid-Task
Sometimes the store doesn't crash so much as get executed. Aggressive battery management can kill the app while it works in the background of a download, and blocked background data starves it mid-transfer — both surface as the same "keeps stopping" dialog.
- Long-press the Play Store icon → App info → Battery and set it to Unrestricted. Samsung (One UI): also check Settings → Battery → Background usage limits and pull the store out of any sleeping-apps list. Xiaomi (HyperOS): Settings → Apps → Manage apps → Google Play Store → Battery saver → No restrictions.
- In App info, tap Mobile data & Wi-Fi and make sure Background data is on.
- While testing, turn Data Saver off (Settings → Network & internet → Data Saver) and disconnect any VPN, so nothing else can throttle the store.
- Restart the phone and repeat the task that used to crash.
One standard reset is worth doing at whichever point you read this: Settings → Apps → Google Play Store → Force stop, then Storage → Clear cache, then reopen the store. It ends a wedged store process and wipes the temporary files a crash leaves behind — nothing you installed is affected.
Reading the Pattern: When and Where It Crashes
Before escalating any further, let the crash tell you its address. Dies only during downloads or updates: storage headroom or the Play Services engine — Fixes 2 and 4. Dies opening app pages or your library: WebView or your account session — Fixes 1 and 3. Started the same day the store updated itself: roll it back — Fix 5. The store, Gmail, Maps, and YouTube all crashing in the same week: that's a shared component failing, or a botched Play Services rollout from Google — those fix themselves within a few days when the corrected build ships, and no setting on your phone speeds it up. If your pattern matches none of these and all six fixes are done, report it inside the app: Play Store → profile icon → Help & feedback. Covers Android 10 through 14.
Watch: Play Store Keeps Crashing Fixed Step by Step
Prefer a walkthrough? This video covers the Play Store app keeps crashing step by step:
Video by Max Dalton — full credit to the creator.
Related Guides:
Mid-Task Crash Questions
Why does the Play Store close in the middle of a download?
Because a download is when the store works hardest: the package has to download, unpack, and install, drawing on Play Services and needing free storage at every stage. If the phone is nearly full or the Play Services data is corrupted, the process dies mid-job — which is why Fixes 2 and 4 come before anything drastic.
The store crashes when I open one particular app's page. Why that page?
App pages are rendered by Android System WebView, and a faulty WebView build can choke on particular page content while other screens load fine. Update WebView — or roll its updates back — using Fix 1; a page-specific crash is the classic signature.
Can't I just reinstall the Play Store?
Not in the usual sense — on most phones it's a system app that can't be removed. Uninstall updates (Fix 5) is the practical equivalent: the store returns to its factory version and then updates itself cleanly, which clears out a bad build without touching your apps or purchases.
By Sameer Zehri | App Fix Guru Editor | Last updated: October 2026
