Fix App Will Not Run Unless You Update Google Play Services

Short answer: This error means an app on your phone is asking Google Play services for something a newer version provides, and the copy on your phone is behind. The fix is almost never the hardware. Open the Play Store, search Google Play Services, and tap Update. If there is no Update button, clear Play services data, reboot, and let the Store re-detect the version. The one case that breaks this pattern is a recent Huawei phone shipped without Google Mobile Services, which needs a different app or a different OS entirely, not a fresh Play services build.

PLAY SERVICES OUT OF DATE

The app is fine. Your Play services are just behind

This dialog is a version mismatch, not a dying phone. An app is asking for a Play services feature your copy does not have yet. Push it to current and the app loads again.

THE FAST FIX

Update from the Play Store

Search Google Play Services in the Store and tap Update; this clears most cases on its own.

THE BACKUP

Clear data, then reboot

Wiping Play services data forces a fresh server-side version check on the next Store open.

THE EXCEPTION

A phone with no GMS

A recent Huawei without Google services needs a different app or OS, not a new build.

Line illustration of an Android phone showing an update Google Play services dialog over a half-loaded app.

The App Will Not Run Unless You Update Google Play Services dialog looks alarming, but it is one of the more honest errors Android throws. It is telling you exactly what is wrong: an installed app has called a Play services API that is newer than the Play services build sitting on your phone. The app refuses to keep going because the plumbing it expects is not there yet. Nothing is broken in the chip or the radio. A number is simply out of date.

That framing matters because it tells you where to look. Google Play services updates on its own track, separate from your Android version, and it does that on purpose so app developers can lean on current Google APIs without waiting for an OS rollout. When the on-device copy falls behind, the gap shows up as this dialog. Push the copy forward and the gap closes.

There is one secondary trigger worth ruling out first. On a few MIUI builds and some region-locked variants, Play services can be switched off rather than out of date. If that is your case, head to Settings, Apps, find Google Play Services, and re-enable it from the Apps screen before you try anything heavier. Everything below assumes Play services is enabled and just needs to catch up.

If your phone is misbehaving in other Play Store ways while you are in here, a few companion fixes are worth keeping open:

The quick fix list

If you have a minute and want the error gone, run straight down this list. The first move resolves most cases, and none of it touches your apps, photos, or messages. Stop as soon as the app you were trying to open loads.

Update Play services in the Store: open the Play Store, search Google Play Services, and tap Update if it is offered.
If there is no Update button: clear the Play Store cache, then search again so the Store re-checks the version.
Clear Play services data and reboot: this re-runs the version check against Google’s servers on the next Store open.
Reopen the broken app: it should now see the current Play services version and start normally.
Only as a last resort: sideload the Google-signed APK from APKMirror, with a signature check, never a random APK site.
Skip all of the above if you are on a recent Huawei phone with no Google Mobile Services; that is a different problem with a different fix.

Update through the Play Store the normal way

Start here, because this is the fix nine times out of ten. Open the Play Store, search Google Play Services, and tap Update. If the button reads Open instead of Update, the Store believes the version on your phone is current even though the app that crashed disagrees. That mismatch is usually a stale Store cache, so clear it: Settings, Apps, Google Play Store, Storage, Clear cache, then search again. The menu path shifts a little by maker, Settings then Apps on a Pixel, Settings then Apps on a Galaxy too, but the destination is the same Storage screen.

On a small number of devices the Google Play Services entry shows up as Disabled rather than out of date. If you see that, tap the entry, tap Enable, then tap Update, and reboot once the install finishes. A reboot after any Play services change is not superstition; it lets the service rebuild cleanly instead of running half-reloaded.

Clear Play services data and let it re-sync

If the Store never offers an Update, force the version check by hand. Go to Settings, Apps, Google Play Services, Storage, Manage storage, then Clear all data. The next time you open the Play Store, Play services re-checks its version against Google’s servers and pulls the current build. Expect to be logged out of Google for a moment; the phone re-syncs on the next open and asks for your password once. That is normal and your account is not going anywhere.

One caveat keeps this step lower on the ladder rather than first: clearing Play services data can also wipe locally cached passwords and saved payment details, so Google lists it as a deeper step for a reason. Treat it as the second pass, not the opening move. After it finishes, reboot. The Play services background process rebuilds its local indices on first launch, which can take a couple of minutes, then settles. Reopen the app that failed and it should detect the fresh version and load.

Manual sideload only as a last resort

Once in a while the Play Store simply refuses to surface the update on a properly registered device. It is rare, but it happens after a botched profile sync or on a phone that has been offline for a long stretch. In that case you can install the Play services APK directly from APKMirror, which mirrors the original Google-signed package and exposes its signing certificate so you can confirm it is the real file before you tap install. Match the certificate to Google’s and you know you are getting the genuine build, not a repackaged one.

Treat this as a genuine last resort and hold the line on where the file comes from. Play services runs with deep system privileges, so a tampered build has near-root reach into every signed-in app on your phone, from banking to mail. That is the whole risk in one sentence: a fake Play services is not a buggy app, it is a key to the rest of your device. APKMirror with a verified signature, or the Play Store itself, and nothing else.

Read this before you sideload

Never grab Play services from a random APK site

It is tempting to search the error and tap the first download link, but Play services is the wrong app to gamble on. Because it holds high system privileges, a malicious replacement has near-root access to everything you are logged into. Use only APKMirror with a signature check that matches Google’s certificate, or the Play Store itself. If you are setting up Google apps on hardware that never shipped with them, our guide to install Google Play covers the supported way to do it.

Devices without Google services

There is one situation where none of the above will help, and it is worth knowing before you spend an afternoon clearing caches. Recent Huawei phones ship without Google Mobile Services at all, a fallout of trade restrictions that pushed Huawei onto its own HMS stack and AppGallery store. On those devices, this dialog is not saying Play services is out of date. It is saying the Google APIs the app wants are simply not present, and no amount of updating will conjure them up.

Your realistic options are two. Run a microG-based setup such as LineageOS for microG, which reimplements enough of the Google APIs to satisfy many apps, or switch to an app that does not depend on Google services in the first place, often available through AppGallery or as an open-source build. Be aware that some apps using Play Integrity, chiefly banking and a few games, may still refuse to run on a microG phone, since they check for genuine Google services rather than a stand-in. Sideloading the real GMS onto a Huawei device technically works, but it breaks often and is supported by neither Google nor Huawei, so it is not a path worth recommending.

If you want to confirm any of this from the source, Google documents its own steps for updating Play services and clearing its cache and data, which is the playbook Pixel support runs internally. The reason a microG phone still trips some banking and game apps is how Play Integrity checks for genuine Google services rather than a stand-in, straight from the Android developer docs. And if you would rather follow a step-through with screenshots, Android Police keeps a tested rundown of how to push Play services to the current version.

The fix in order, step by step

Here is the whole sequence in one place. Work it from the top and stop the moment the app loads; there is no reason to run the heavier steps once a lighter one has already fixed it.

Update from the Play Store. Search Google Play Services and tap Update; if the button says Open, clear the Store cache and search again.
Clear Play services data if Update never appears. Settings, Apps, Google Play Services, Storage, Clear all data, mindful of the cached-password caveat.
Reboot. Power off, wait, power on, so the service rebuilds its indices cleanly.
Reopen the broken app. It should detect the current Play services version and start normally.
Sideload only if the Store will not. APKMirror with a verified Google signature, never a random APK site.

Cause and fix at a glance

Different starting symptoms point to different rungs on the ladder. Find the row that matches what you are seeing, then jump straight to the matching step above instead of grinding through every fix.

What is going on	The fix
App calls a newer Play services API	Update Play services from the Store
Store shows Open, not Update	Clear the Play Store cache, then search again
No Update button at all	Clear Play services data, then reboot
Play services entry shows Disabled	Tap Enable, then Update, then reboot
Store will not surface the update	Sideload the Google-signed APK from APKMirror with a signature check
Recent Huawei phone, no GMS	Use microG or a Google-free app, not a Play services update

Common questions

Why does this error show up right after a phone reset? A fresh setup installs Play services at a baseline version, then the Play Store updates it in the background over the next little while. If an app outruns that background update, you see the dialog. Open the Play Store and trigger the Play services update by hand to skip the wait.

Can I use the app without Play services at all? Sometimes. Apps with Huawei AppGallery builds or open-source alternatives often run fine without it, and a microG setup covers a good slice of the rest. Most mainstream apps that lean on Google sign-in, push, or maps will not, so check whether a Google-free build of your specific app exists.

Will clearing Play services data delete my Google account? No. The account stays linked to the phone. Clearing data only resets the local Play services cache and indices, then re-syncs and asks for your password once. The one thing to watch is locally cached passwords and payment details, which can be cleared along with it, which is why it is a later step rather than a first one.

Does any of this hurt battery life? Briefly. A freshly cleared Play services draws a little extra power for a few hours while it rebuilds its indices, then settles back to normal within a day. If the drain lingers past that, the cause is almost certainly something else on the phone, not Play services.

The bottom line

Strip away the scary wording and this is a version problem with a short fix. The app wants a newer Play services than the one on your phone, so you push Play services to current through the Store, and if the Store is being stubborn, you clear its data and reboot to force the check. Two passes clear the vast majority of cases.

The only genuinely hard case is a phone with no Google services to update, a recent Huawei being the common example, where the answer is a different app or a different OS rather than a different Play services build. Everything else comes down to getting one number up to date, then letting the phone settle.

How we put this together

Reproduced on Pixel and Galaxy, checked against Google’s docs

We triggered the Play services version dialog on a Pixel and a Galaxy across current Android 15 and 16 builds, then worked each fix back from a real failure rather than describing it in theory. Every menu path and the order of the ladder were cross-checked against Google’s own Play services support documentation, and the Huawei carve-out was verified against how microG and Play Integrity actually behave on devices without Google Mobile Services. When behavior changes on a new release, we revisit the steps rather than leaving stale instructions in place.