You tap the Play Store icon and, before the storefront even loads, a grey dialog takes its place: "Google Play Store keeps stopping" — with two buttons, App info and Close app. You tap Close app. You tap the icon again. Same dialog. That loop is the whole experience now, and it locks you out of far more than one app: while the store dies on launch, nothing on the phone can be installed or updated, including the update your banking app keeps asking for.
Understand what the message claims, because it points at the fix. "Keeps stopping" means the app's process crashes the moment it starts. This is not a connection error, and your account is not banned. A crash-on-launch almost always traces back to bad local data the store reads during its first seconds: its own cache or data, the Play Services engine it calls at startup, or a store update that arrived broken. The eight fixes below repair that startup path in order.
Quick Answer: Go straight to the store's own data: Settings → Apps → Google Play Store → Force stop, then Storage & cache → Clear cache. Still stopping? Tap Clear data on the same screen, and clear the cache of Google Play Services as well. If the crashes began within a day of the Play Store updating itself, skip to Fix 4 and roll that update back instead.
Fix 1: Force-Stop the Store and Clear Its Cache
The cache is among the first things the store reads when it launches, so a corrupted entry there can kill the app before any screen appears. Force-stopping first matters: it ends the crashed process completely instead of leaving a half-dead one for the store to trip over again.
- Open Settings → Apps → See all apps (Samsung: Settings → Apps; Xiaomi: Settings → Apps → Manage apps).
- Open Google Play Store and tap Force stop.
- Tap Storage & cache, then Clear cache.
- Open the Play Store and see whether it survives its own launch.
Fix 2: Wipe the Store's Data for a Clean Start
If the cache wasn't the corrupted piece, the store's data may be — it holds the store's settings, preferences, and a local database of your library that the app rebuilds by reading it at startup. Return to the same Storage screen and tap Clear data (labelled Clear storage on Samsung). The store then behaves as it did on first run: you'll accept the terms once more, and your download preferences reset. Your installed apps, purchases, and app data are not touched — only the shop's own notebook is thrown away.
Fix 3: Reset Google Play Services, the Engine the Store Starts With
The storefront is mostly a window. In its first seconds of life it hands sign-in, licensing, and downloads to Google Play Services — and if that component's data is corrupted, the store crashes while calling it, wearing the blame itself. Clear the engine, not just the window:
- Go to Settings → Apps → Google Play Services → Storage & cache.
- Tap Clear cache and test the Play Store.
- Still crashing? Go back and tap Manage space → Clear all data (or Clear storage).
- Restart the phone, give Play Services a minute to re-sync, and open the store.
Expect a short settling period after a Play Services data clear: a few apps may re-request permissions, and payment apps can ask you to confirm a card again. That is the reset completing, not new damage.
Fix 4: Roll Back a Play Store Update That Arrived Broken
Use timing as your clue. The Play Store updates itself silently in the background, and if the dialog loop began within a day of such an update, the update itself is the prime suspect — no cache clear repairs a buggy build. Roll it back: Settings → Apps → Google Play Store → ⋮ (three dots, top right) → Uninstall updates. The store returns to its factory version and, in the faulty-update scenario, opens immediately. Don't worry about staying behind: the store will update itself again over the following hours, and the build it fetches is usually the corrected one.
Fix 5: Correct the Clock Before It Fails the Store's Security Check
At launch, the store verifies security certificates with Google's servers, and certificates are only valid inside a window of time. A phone clock that has drifted — after the battery ran completely flat, a manual change, or travel across time zones — falls outside that window, and the store may abort its own startup rather than connect insecurely. Go to Settings → System → Date & time and switch on Set time automatically and Set time zone automatically. If both were already on, toggle them off and back on to force a fresh sync, then restart the phone and try the store again.
Fix 6: Refresh the Google Account the Store Signs In With
Part of the store's launch routine is signing in with your Google account, using a token stored on the phone. When that token desynchronises, the store can die right at the sign-in step. Removing the account and adding it back forces a completely fresh handshake:
- Open Settings → Passwords & accounts (Samsung: Accounts and backup → Manage accounts), tap Google, then your account.
- Tap Remove account and confirm — and be sure you know the account password before you do.
- Restart the phone, so the stale session leaves memory entirely.
- Return to the same screen, tap Add account → Google, and sign back in.
Nothing in the account itself is deleted: mail, contacts, and purchases live with Google and sync back down.
Fix 7: Make Sure the Store Has Room to Work and a Current System
A phone with almost no free storage stalls its own system processes, the store included. Check Settings → Storage and free space until at least 1 GB is available — delete unused apps and clear out the Downloads folder first. Then check Settings → System → System update (Samsung: Software update) and install anything pending: system updates routinely carry Play Services fixes, and an out-of-date system paired with a current store is a mismatch that produces exactly these launch crashes.
Fix 8: Use Safe Mode to Catch an Interfering App
If the store still dies, find out whether something you installed is killing it. Hold the power button, then long-press Power off on screen and choose Safe mode. In Safe Mode, only system apps run. If the Play Store opens normally there, a third-party app is the culprit — VPNs, ad-blockers, and aggressive "cleaner" apps are the usual offenders. Restart normally to leave Safe Mode, then uninstall your most recent additions one at a time, testing the store after each, until the loop stops.
When Every Google App Is Crashing, Not Just the Store
Step back and check the pattern. If Gmail, YouTube, and Maps are also dying on launch, the fault is not in the store at all — it sits in Play Services or the system layer beneath all of them. Repeat Fix 3's full data clear, install any pending system update, and restart. Only if the crashing survives all of that is a factory reset worth discussing, and even then: back up first (Settings → System → Backup), and treat it as the end of the road. If Google apps still crash on a fresh system, the problem is account-side or hardware-side — contact Google Play support from play.google.com → Help → Contact us and tell them which fixes you've already run. Covers Android 10 through 14.
Watch: Play Store Keeps Stopping Fixed Step by Step
Prefer a walkthrough? This video covers the 'Play Store has stopped' problem step by step:
Video by XFix — full credit to the creator.
Related Guides:
Plain Answers About a Store That Won't Stay Open
Will clearing the Play Store's data delete my installed apps?
No. Fixes 1 and 2 only reset the store app itself — its cache, settings, and local library database. Every installed app, its data, and your purchase history stay exactly where they are; you'll just accept the store's terms once more.
Why does it crash instantly, before I can even search for an app?
Because the corruption sits in data the store reads during startup — its cache, its local database, or the Play Services data it calls in its first seconds. The app never reaches the part where you could search. That's why the fixes concentrate on startup data rather than on settings inside the store.
Is it safe to uninstall Play Store updates?
Yes. It simply returns the store to the version your phone shipped with (Fix 4); nothing else is removed, and the store updates itself again automatically. If a faulty update caused the crash loop, the factory version is often the fastest way out of it.
By Sameer Zehri | App Fix Guru Editor | Last updated: October 2026
