Fix Android 'Unfortunately, Google Play services has stopped'

Fix 1: Clear Cache and Data for Google Play services

This is the #1 fix because the error usually comes from a corrupt cache that Google Play services left behind. Every time you open an app that uses Google Maps, Gmail, or even the Play Store, Play services runs in the background. Over time, that cache can get corrupted, especially after an OS update or a bad app install.

Here's how to clear it:

1. Open Settings on your phone.
2. Tap Apps or Application Manager (the name varies by Android version).
3. Scroll down and tap Google Play services. If you can't find it, tap the three-dot menu and enable Show system apps.
4. Tap Storage & cache (or just Storage on older Androids).
5. Tap Clear Cache first. Don't clear data yet—cache is usually enough.
6. After clearing cache, go back to the app info screen and tap Force Stop.

What you should expect: After clearing cache, the error might not appear immediately. But to be thorough, restart your phone. Once it boots up, try opening a Google app or any app that uses Play services. If the error is gone, you're done. If it persists, move to Fix 2.

If clearing cache doesn't work, you can also try Clear Storage (or Clear Data). This resets Play services to its default state. It won't delete your personal data, but it will sign you out of some Google apps temporarily. So re-enter your Google account in Settings > Accounts after doing this.

Fix 2: Update Google Play services and Android System WebView

Sometimes the error appears because your Google Play services version is outdated or has a bug that Google fixed in a newer release. Also, Android System WebView is a separate component that many apps use for rendering web content. A mismatch between Play services and WebView can trigger the exact same error.

Here's what to do:

1. Open the Google Play Store app.
2. Tap your profile icon (top right) and then tap Manage apps & device.
3. Tap the Updates available tab. Look for Google Play services. If it's listed, tap Update next to it.
4. Do the same for Android System WebView if it shows an update.
5. If you don't see them under Updates, tap Search at the top, type “Google Play services,” and open its page. If there's an Update button, tap it.

After updating: Restart your phone again. When you open an app that previously crashed, the error should be gone. If you don't have any updates available or the error persists, move to Fix 3.

A quick tip: some Samsung and Xiaomi phones have a setting that automatically updates apps only on Wi-Fi. If you're not on Wi-Fi, Play services won't update. Check that your phone is connected to Wi-Fi or that mobile data updates are allowed in the Play Store settings.

Fix 3: Reset App Preferences (or clear cache for all Google apps)

If you're still seeing the error, there's likely a conflict with app permissions or default apps. Resetting app preferences won't delete any app data, but it will reset disabled apps, notification restrictions, and default app settings. This can fix the issue if, for example, a default dialer or SMS app is misbehaving and interfering with Play services.

How to do it:

1. Go to Settings > Apps (or Application Manager).
2. Tap the three-dot menu (top right) and choose Reset app preferences.
3. Read the warning—it's just informational—and tap Reset apps to confirm.

After you reset: You'll need to re-enable any apps you had disabled (like some bloatware) and set your default browser or phone app again if you had changed them. But it doesn't touch any of your personal data.

If that still doesn't help, the last resort is to clear the cache on all Google apps at once. Go to Settings > Storage > Other apps (or Storage > Apps), then tap each Google app (Play Store, Gmail, Google, etc.) and clear its cache. Restart your phone. This is a bit tedious but often works when nothing else does.

A real-world trigger: I've seen this error pop up on a Pixel 6 right after a monthly system update. The update interrupted Play services in the background, and clearing its cache fixed it instantly. On a Samsung Galaxy A50, updating WebView did the trick after the cache clear failed.

Quick-reference summary table