Android error 504: what it means and how to fix it
Error 504 in Google Play appears when an app fails to download or install, and it borrows its number from HTTP's gateway timeout: somewhere between the Play Store app, Google's servers, and the phone's account framework, the handoff timed out or broke. In practice it clusters around the Google Services Framework and Play Store data becoming inconsistent, which is why its fix list overlaps heavily with errors 492 and 944 while adding a few account steps of its own.
What causes it
- Corrupted or stale data in Google Services Framework or the Play Store.
- A download process interrupted and left in a bad state.
- Account authentication on the device gone stale.
- A genuinely poor or filtered connection during the download stage.
Fix it, in order
- Restart the phone and retry on a solid Wi-Fi connection. Rule out the simple timeout first, since the code's literal meaning is one.
- Clear cache and data for Google Play Store (Settings, Apps, Google Play Store, Storage).
- Clear cache and data for Google Services Framework and Google Play services. Error 504 lives in the framework's download coordination more often than in the store's front end.
- Check date and time are automatic. Authentication behind downloads fails quietly on a wrong clock.
- Remove and re-add your Google account if the clears did not work: remove, restart, sign back in, then download. This is the heavy step and the one that ends persistent 504s.
- Free up storage and confirm several hundred megabytes of headroom; installs that run out of room mid-write can surface as download errors rather than space errors.
The account step needs your password and possibly a verification code. Have them ready before removing the account, and expect contacts, mail, and calendar to re-sync afterwards.
Common questions
Is Android error 504 the same as HTTP 504? It is named after the same idea: a gateway-style timeout in a chain of handoffs. On Android the chain is the Play Store talking through Google's services framework to the servers. The number is shared; the machinery is the phone's, not a website's.
Why does 504 affect updates of one app only? Updates re-use the app's existing download records and permissions state. A corrupted record makes that one app's update fail repeatedly while fresh installs of other apps, using clean records, succeed.
Related errors