Usually there is no problems with downloading applications from the Google Play. However, sometimes it can happened, that the message “Update could not be downloaded due to an error 492” pops up in Play Store. Therefore you need to know why is it happened and how to fix error 492 google Play Store.
Why do some applications are loaded normally, while others produce an error 492 on android? The problem comes with the applications that are used to install Java, otherwise also known as Dalvik cache. How to fix the error on the play 492 Market?
Problems causing by 492 error Play Store can be solved with the methods, which are described bellow:
First way to fix 492 error is the easiest. Remove the application, and then reinstall it.
If it is installation for the first time, you should try to stop the downloading, close Google Play Store, open it one more time and try downloading the app all over again.
If Play Store error 492 popped up during the application updating, you should uninstall and reinstall it all over again, which might resolve the problem.
If this method did not work, then go to the second one.
SD cards can be the cause error 492 Play Store pop up. If you have already used all other methods, but still facing the error code 492, it is necessary to format your SD card.
Do not forget to make sure that you stored all important data from the SD card on the PC before the formatting.
First, open the “Settings”, then “Apps” and find Google Play Store. There you need to choose on the “Storage” and press the “Clear Cache”.
Second step is to open the Google Play Services in the “Apps” and repeat the manipulations that were done for the Google Play Store.
Reopen the Google Play Store and try to download the app once more.
If you could not resolve the error 492 Play Store with previous methods help, then it is necessary to do Factory data reset.
To do this you need to open “Settings > Backup & Reset” and click on “Factory data reset”.
The device will be fully cleared from all data that can cause google play store error 492 after rebooting Android.