. iExplorer « Torchwood Archives
Torchwood Archives
23Apr/12Off

“Item” and 22 other items could not be purchased

"EVE: Templar One" and 22 other items could not be purchased at this time. Please try again later.

If you own an iDevice running iOS 5 or 5.1 you might have seen this window when trying to update or download an app from the App Store:

And if you've seen it, you've probably seen it more than once. So what does this error message really mean?

It means that you have a corrupted sqlite db file. Who would have thought? Unfortunately this is a known bug and has been happening to users all over the world. So far Apple did not fix the issue, but thanks to the internet, some clever folks have found & shared the solution on apple.com community forum.

EDIT:Apple has adressed this bug in IOS 5.1.1

If you are experiencing the problem above, just go to Settings -> General -> Software Update to update your device to iOS 5.1.1

If for whatever reason you can not/don't want to update your device, follow the tutorial below.

The tutorial is based on the forum info, but has some screenshots, which should make it even easier.

Pre-requisites

iOS version <= 5.1 (bug has been fixed by Apple in iOS 5.1.1 and above) - but jailbreak is not required!

The guide

1. Download iExplorer from their creator's website: http://www.macroplant.com/iexplorer/

2. Install iExplorer to your PC or Mac

3. Run iExplorer

4. Connect your iPhone or iPod Touch or iPad to your computer

5. Close iTunes if it starts automatically

6. Click "Mount iDevice" in the iExplorer window. You should now see list of files in the sandbox part of the device storage:

7. Browse to "Media" ->; "Downloads"

8. Find the file "downloads.*.sqlitedb"

9. Delete the file mentioned in 8.

10. Close iExplorer

11. Disconnect the device

12. Press the top "On/off" button and keep it pressed until "Slide to power-off" appears. Once it does, move the slider.

13. Wait for the device to shut down

14. Press the "On/off" button and wait for the device to boot up.

Done! The bug should be gone.

.

Credits

Writing this guide was possible thanks to just_jeepin and ya1950 posts on Apple Support Communities forum.