How to fix Nexus 7 app update errors after installing Android 4.2

How to fix Nexus 7 app update errors after installing Android 4.2
Overall, the Android 4.2 update seems to be going pretty well and hasn't had any major bugs that have been reported yet, but Nexus 7 owners have been reporting a minor, but annoying error after installing the update. Apparently, some users have found that after installing the Android 4.2 update, the Google Play Store won't be able to update apps and will keep giving an error, which reads that the update couldn't be downloaded because of an error. 

Luckily, there is an easy fix if you've come across this problem. It seems that it's a problem with the Google Account information, so all you have to do is go into Settings>Accounts, delete your Google account, then reboot your device, and re-enter your Google account info. Simple as that. 

It should only take a couple minutes, and then you'll be right back to updating apps without any issue. 

source: Droid Life

How to fix Nexus 7 app update errors after installing Android 4.2

Related phones

Nexus 7
  • Display 7.0" 1280 x 800 pixels
  • Camera / 1.2 MP front
  • Processor NVIDIA Tegra 3 T30L, Quad-core, 1300 MHz
  • Storage 8 GB
  • Battery 4325 mAh

FEATURED VIDEO

7 Comments

1. protozeloz

Posts: 5396; Member since: Sep 16, 2010

Wait, there is a shadowgun update?

2. kcombs

Posts: 275; Member since: Dec 15, 2010

mine is updating fine.

3. MobileCaseReview

Posts: 242; Member since: Feb 10, 2012

You can also go into manage apps>google play store>clear data & cache then manage apps>google services framework> clear data then reboot. if you're rooted, also, clear cache and dalvik, fix permissions and reboot after.

4. Aeires unregistered

Must be isolated instances, just updated three apps flawlessly.

5. imkyle

Posts: 1111; Member since: Nov 18, 2010

This happened to my Galaxy Nexus while i cleared the framework before 4.2was installed. This cleared it perfectly.

6. cheetah2k

Posts: 2146; Member since: Jan 16, 2011

No problems here either (in Australia)

7. JonBjSig

Posts: 176; Member since: Nov 17, 2011

This happened to me after the 4.1.2 update, I think it happens when you use the Google Services Framework clear data + force stop trick to try and force the update.

Latest Stories

This copy is for your personal, non-commercial use only. You can order presentation-ready copies for distribution to your colleagues, clients or customers at https://www.parsintl.com/phonearena or use the Reprints & Permissions tool that appears at the bottom of each web page. Visit https://www.parsintl.com/ for samples and additional information.