Don’t Update Kindle for iPhone or iPad, Bug Wipes Book Library
Don’t update to the latest version of Kindle for the iPhone or iPad unless you want to gamble with losing all the books on your device.
The latest Kindle 3.6.1 update to hit the app store has an issue that can wipe the Kindle library off your iPhone or iPad and force you to re-register the device with Amazon.
When Gotta Be Mobile staff opened up their Kindle apps this morning one member was still able to use his library, but another had to re-setup their account, register the iPhone with Amazon again and sort through a long library of books to re-download them again.
The update also wiped out saved settings and bookmarks for some users. Here are a sample of angry users who updated.
Today’s (26 Feb 2013) upgrade erased all content on my iPad, including all of my bookmarks. What gives? – Geoff.Alexander
The update deleted all books from my iPad, and I had to register again, creating a second name for the same iPad. It’s like starting all over again. Now I have to upload over 130 books from the cloud. – Equinebob
Thank you new update for erasing all of my saved settings. Now I have to go through my hundreds of books to find the ones I haven’t read and change all of my screen settings. – ShannonNoel
When we re-downloaded our library Amazon Cloud and Whispersync kept our progress, and we did not need to re-purchase books so the issue is more about annoyance than a loss of money. Though users who lost bookmarks have it much worse, especially if those bookmarks are part of any school or work projects.
Amazon has posted a small warning on the update description, which says,
Note: There is a known issue with this update. If you are an existing Kindle for iOS user, we recommend you do not install this update at this time
But, the update is still available for users to download from iTunes and users who hit update all or who do not expand the changes on an iPhone won’t see this update.
For now, avoid updating Kindle for iPhone and iPad until Amazon pushes an updated version that removes this issue. If you have already downloaded the update, you can try to wait it out, but we aren’t sure if that will help, so you may want to bite the bullet and check.