How to Fix Google Play Store Error 504
What error 504 means
Error 504 is a Google Play Store error that blocks app downloads with the message “App could not be downloaded due to an error. (504).” It often appears at an especially frustrating moment — right as a download is about to finish — because the failure happens when the Play Store tries to finalize and verify the download rather than when it starts.
Under the hood, 504 behaves like a timeout error: the store’s download request to Google’s servers gets interrupted or never gets a clean response, so Android gives up and reports the failure. That makes this error different from storage errors or account errors — the app, the network, and your account can all be perfectly fine, and the download still fails because the temporary data the Play Store keeps about the download got corrupted or the connection timed out.
The good news is that error 504 responds well to the classic Play Store repair routine. Because the cause usually lives in the store’s own data — corrupted cache, stale Services Framework state, or a broken account handshake — clearing that data out and forcing a fresh start fixes it in the vast majority of cases. Most people get past error 504 in under fifteen minutes without losing any apps or data.
Common causes
- Corrupted Play Store cache or data: broken temporary download files or a data collision inside the Play Store app — the most common cause of 504.
- Stale Google Services Framework data: the behind-the-scenes framework that identifies your phone to Google can hold bad state that poisons every download.
- Google account sync glitch: a broken account handshake between your phone and Google’s servers can interrupt downloads even when the store itself is healthy.
- Slow or unstable network: because 504 is a timeout-class error, weak Wi-Fi or flaky mobile data that stalls mid-download can trigger it directly.
- Nearly full storage or wrong device time: critically low internal storage can abort the final install step, and an incorrect system clock can make secure download connections fail.
How to fix error 504 — step by step
Work through these fixes in order. Most people are fixed by step 4.
- Restart your phone. Press and hold the Power button (or swipe down from the top of the screen and tap the power icon), then tap Restart. A reboot clears temporary glitches in the Play Store’s download processes and gives any stalled network request a fresh start. Once the phone is back on, open the Play Store and try the download again — this alone resolves error 504 when the cause was a one-time timeout or hiccup.
- Clear the Google Play Store’s cache and data. Open Settings, then go to Apps (or Apps & notifications), then See all apps. Tap Google Play Store, then Storage & cache. Tap Clear cache first, then Clear storage (or Clear data) and confirm. This wipes the store’s temporary download state and corrupted files without touching your installed apps, photos, or your Google account. Reopen the Play Store and retry the download.
- Clear data for Google Services Framework and Google Play Services. Stay in Settings > Apps > See all apps and tap the three-dot menu to choose Show system apps. Open Google Services Framework, tap Storage & cache, then Clear data — stale data here is one of the classic causes of error 504. Then go back and open Google Play Services and tap Clear cache. Restart your phone after clearing both, then try the download again.
- Remove and re-add your Google account. Go to Settings > Passwords & accounts, tap your Google account, then Remove account. Restart the phone, then go back to Settings > Passwords & accounts, tap Add account > Google, and sign in again with the same account. This refreshes the account handshake between your phone and the Play Store, which fixes the data-collision problems that can keep error 504 alive.
- Switch networks and check your storage. Error 504 is a timeout-class error, so a slow or unstable connection can trigger it. If you’re on Wi-Fi, try mobile data (or vice versa), and move closer to the router or toggle Airplane mode on and off to force a fresh connection. Also check Settings > Storage — if internal storage is nearly full, downloads can stall and fail, so free up space by deleting unused apps and large files.
- Wipe the cache partition and check date and time. Power off your phone, then hold Power + Volume Up together until the recovery menu appears (on Samsung phones, hold them while the phone is connected to a charger or computer). Use the volume buttons to highlight “Wipe cache partition,” press Power to select it, confirm, then choose “Reboot system now.” Also go to Settings > System > Date & time and make sure Set time automatically is on — a wrong clock can make secure download connections fail. A factory reset is the absolute last resort, and you should back up everything first.
Did this fix it? Quick checklist
- The app downloads without the 504 pop-up
- Downloads complete and install successfully
- The Play Store opens, browses, and searches normally
- No “App could not be downloaded” errors on retry
If error 504 still appears after all six steps, try switching networks (Settings > Network & internet) — some workplace or school Wi-Fi networks interfere with Play Store traffic — and as a final measure, back up your data and consider a factory reset (Settings > System > Reset options > Erase all data).
Frequently asked questions
What does Google Play Store error 504 mean?
Error 504 means the Play Store couldn’t finish downloading an app — you’ll see “App could not be downloaded due to an error. (504)” when the download fails. It’s usually caused by corrupted Play Store or Services Framework data, a Google account sync problem, a timeout from a slow network, or nearly full storage.
Will clearing Play Store data delete my installed apps?
No. Clearing cache and storage for the Google Play Store only removes the store’s temporary files and settings — your installed apps, photos, and personal files stay exactly where they are. You’ll just need to accept the Play Store terms again when you reopen it.
Why does error 504 happen when a download is almost finished?
Error 504 is closely tied to the moment a download should finalize — corrupted temporary download data, stale Google Services Framework state, or a connection that times out while the store is verifying the download can all trigger it right at the end. That’s why clearing the store’s cache and data is the most effective first fix.
Do I need a factory reset to fix error 504?
Almost never. Restarting your phone, clearing the Play Store and Services Framework data, or re-adding your Google account fixes error 504 in nearly every case. A factory reset is only worth considering if every other step has failed, and you should back up all your data first.