http://tidbits.com/ Updating to version 3.6.1 of the Kindle app removed books from your device and marked them as New when you re-downloaded them from Amazon’s cloud. Fortunately, a quick 3.6.2 update fixed the issue. But why would this come up in the first place? en-us Copyright 2013 TidBITS Publishing Inc. Tue, 05 Mar 2013 00:00:00 EST Tue, 05 Mar 2013 00:00:00 EST editors@tidbits.com (TidBITS Editors) editors@tidbits.com (TidBITS Editors) http://tidbits.com/images/tb_logo_152x55.png http://tidbits.com/ 55 152 TidBITS badge http://db.tidbits.com/article/13590?rss#comments_17853 Tue, 05 Mar 2013 02:25:44 EST http://tidbits.com/article/13590#comments_17853 http://db.tidbits.com/article/13590?rss#comments_17848 Mon, 04 Mar 2013 18:54:05 EST http://tidbits.com/article/13590#comments_17848 http://db.tidbits.com/article/13590?rss#comments_17847 Mon, 04 Mar 2013 18:50:17 EST http://tidbits.com/article/13590#comments_17847 If you update by way of the App Store on the iOS device AND then sync with iTunes, then the old version will still be in the trash after the sync. While you will have the new version on the iOS device, if you have not emptied the trash yet (and in this case, not opened the Kindle app), you can find the old version in the trash and revert to the old version.
I know this because I don't empty my trash too often on the Mac that I sync my iOS devices with and there are currently 191 iOS apps in the trash (yes, it has been a while since I emptied the trash)...including the old version of the Kindle app.]]> http://db.tidbits.com/article/13590?rss#comments_17840 Mon, 04 Mar 2013 09:16:25 EST http://tidbits.com/article/13590#comments_17840 http://db.tidbits.com/article/13590?rss#comments_17835 Fri, 01 Mar 2013 09:11:38 EST http://tidbits.com/article/13590#comments_17835
The incident has changed how I do updates: now I open the "more" information before hitting Update All.

Note: if you do the mores bottom up, there's less scrolling involved.]]> http://db.tidbits.com/article/13590?rss#comments_17830 Wed, 27 Feb 2013 18:52:53 EST http://tidbits.com/article/13590#comments_17830
This isn't true. The developer can reject the binary themselves in the week that the app spends in Apple's queue. And once Apple's approved it, the developer gets a second chance to reject it (assuming they chose to have this chance; you can bypass this one).

Surely Amazon should have noticed this bug in that week.

But even after the developer releases the app, they can pull it. They can't wind back to the previous version, but they can prevent further damage.

I say this as a developer who's shipped a bad update. Apple doesn't deserve blame, and Apple didn't force me to release the app.]]> http://db.tidbits.com/article/13590?rss#comments_17822 Wed, 27 Feb 2013 11:40:57 EST http://tidbits.com/article/13590#comments_17822 http://db.tidbits.com/article/13590?rss#comments_17821 Wed, 27 Feb 2013 11:37:58 EST http://tidbits.com/article/13590#comments_17821 http://db.tidbits.com/article/13590?rss#comments_17819 Wed, 27 Feb 2013 10:14:57 EST http://tidbits.com/article/13590#comments_17819 http://db.tidbits.com/article/13590?rss#comments_17818 Wed, 27 Feb 2013 09:53:50 EST http://tidbits.com/article/13590#comments_17818 http://db.tidbits.com/article/13590?rss#comments_17817 Wed, 27 Feb 2013 09:52:08 EST http://tidbits.com/article/13590#comments_17817 http://db.tidbits.com/article/13590?rss#comments_17816 Wed, 27 Feb 2013 09:40:53 EST http://tidbits.com/article/13590#comments_17816
I do agree with the app store issues though. Another pet peeve of mine is that on older iOS devices, App updates which clearly cannot run on the device (example: iOS 5.1) are still listed, with no way of hiding them for that particular device.]]> http://db.tidbits.com/article/13590?rss#comments_17815 Wed, 27 Feb 2013 09:37:29 EST http://tidbits.com/article/13590#comments_17815