How to Fix Google Play Store Error 492 "App Could Not Be Downloaded"

By FixMyError · Updated October 17, 2026 · 6 min read

What "Error 492" means

Error 492 is one of the Google Play Store's oldest numbered download failures, and it still shows up on modern Android phones. You tap Install or Update, the download begins, and then it dies with the message "App could not be downloaded due to an error. (492)". It can strike a single app or every download on the phone at once, and it is just as likely to hit updates as fresh installs. Your connection is usually fine — the Play Store and the rest of your apps behave normally, which tells you the problem lives in the download pipeline itself, not in your network.

Behind the scenes, installing an app is a chain of handoffs. The Play Store talks to Google Play Services, the Google Services Framework, and the Download Manager to fetch the app package, stage it in storage, and hand it to Android's installer. On top of that, Android keeps a Dalvik or ART cache — pre-compiled runtime files that apps need to launch. When any link in this chain builds up corrupted data, the whole pipeline stalls and the Store reports error 492. That is why the fix sequence below clears each link in order: the Store first, its helper services second, the system cache third, and storage space last.

Common causes

• Corrupted Play Store cache or data: the most common trigger — stale or damaged temporary files make the Store fail its own download routine.
• Damaged helper-service data: corrupted cache in Google Play Services, the Google Services Framework, or the Download Manager breaks the install pipeline.
• Corrupted Dalvik or ART cache: the classic error-492 culprit on older phones — stale runtime caches make every new download fail the same way.
• Low internal storage: the Store needs scratch space to stage downloads; a nearly full phone can throw error 492 even with clean caches.
• Buggy Play Store update: an automatically installed Store update can itself introduce the bug that causes error 492.
• Google account sync glitch: an account whose sync state is wedged can make downloads fail repeatedly with the same code.

How to fix "Error 492" — step by step

Work through these fixes in order. Step 1 takes a minute; most people are fixed by step 2, and the Dalvik-cache wipe in step 4 is the signature fix for this error.

1. Clear the Google Play Store's cache and data. Open Settings, go to Apps, find Google Play Store, tap Storage, then tap Clear cache and Clear data. Corrupted cache files are the single most common cause of error 492, and this clears them out. Restart your phone and try the download again.
2. Clear cache and data for Google Play Services, Google Services Framework, and Download Manager. The Store never works alone, so repeat the same routine for its helpers. In Settings, then Apps, find Google Play Services, Google Services Framework, and Download Manager one by one, and for each tap Storage, then Clear cache and Clear data. Restart the phone and retry the download.
3. Free up internal storage space. Error 492 can appear when the phone is nearly full. Go to Settings, then Storage, and check your free space. Delete unused apps, empty the Downloads folder, and back up old photos or videos until you have at least a gigabyte free, then try installing again.
4. Wipe the cache partition (Dalvik cache) from recovery mode. Error 492 is classically tied to a corrupted Dalvik or ART cache, especially on older phones. Power off the phone, then hold Power and Volume Up together until the recovery menu appears. Use the volume keys to highlight Wipe cache partition and the Power button to select it. This removes stale system caches without touching your files or apps. Reboot and retry the download.
5. Uninstall updates for the Google Play Store. A buggy Store update can introduce error 492. Go to Settings, then Apps, tap Google Play Store, tap the three-dot menu in the top corner, and choose Uninstall updates. Open the Play Store afterward — it will update itself in the background — and try the download again.
6. Remove and re-add your Google account, then restart. If nothing above helps, reset the account layer. Go to Settings, then Accounts (or Passwords and accounts), tap your Google account, and choose Remove account. Restart the phone, add the account back, and open the Play Store. This clears wedged sync state that can keep error 492 stuck on one account.

Did this fix it? Quick checklist

• The Play Store downloads and updates apps without the 492 error
• The Play Store, Play Services, and Download Manager caches were all cleared
• The cache partition was wiped from recovery mode
• The phone has a comfortable amount of free internal storage

If you've worked through all six steps and error 492 still appears, the problem sits below the software layer: failing internal storage, a device-specific firmware bug, or — on some older models — a Dalvik cache that rebuilds corrupted on every boot. Back up your data and check whether your phone's manufacturer has a software update or support thread about Play Store 492 errors for your model, and consider a factory reset as a last resort before visiting a service center.