Skip navigation

An unknown error has occurred app store

172569 Views 166 Replies Latest reply: Mar 13, 2014 10:44 AM by matt.m.edwards RSS
  • carnecro Calculating status...
    Currently Being Moderated
    Oct 4, 2012 10:49 AM (in response to Andreas Amann)

    You can remove the cookie directly in your account (`rm Library/Cookies/com.apple.appstore.plist`), when AppStore starts new cookie will be created. I think it's one of many hints in this thread and it does not work for me

  • unixy_goodness Calculating status...
    Currently Being Moderated
    Oct 4, 2012 11:05 AM (in response to carnecro)

    One more data point, which I encountered on another machine. I'd see updates, but the App Store would just lock up with the spinning pizza of death.

     

    In the console log, I saw a bunch of messages along the lines of:

    Sandbox creation failed: Saving after update for container (~/Library/Containers/com.apple.ShareKitHelper/Data) failed: NSCocoaErrorDomain:513 You don’t have permission to save the file “Container.plist” in the folder “com.apple.ShareKitHelper”.

     

    Doing an ls -le on that file showed that there were complicated ACLs. It was probably the wrong thing from a security standpoint, but I removed them all and the App Store started working again:

     

    chmod -R -N /Users/samuelg/Library/Containers/com.apple.ShareKitHelper

     

    This worked for me. I don't know how I got bad ACLs on the directory or its contents. Disk Utility's "repair permissions" doesn't seem to look into the user's Library directory or fix problems there.

     

    It's conceivable to me that your Library/Cookies directory has bad ACLs on it.

     

    If you try:

     

    ls -lde ~/Library/Cookies

     

    and you see something like:

     

    -rwxrwxrwx@ 1 yourname  staff  66801 Sep 12 13:48 /Users/yourname/Library/Cookies

    0: group:everyone deny write,append,writeattr,writeextattr,chown

     

    you might try removing the ACLs. I don't really know the overall security implications -- I suspect it's not the safest thing to do -- but it might be at least an indicator of what's wrong. If it works, you can always try restoring ACLs one by one, so it's as locked down as possible but still functional.

     

    I'm shooting in the dark somewhat, so keep that in mind. I know a decent amount about Unix, but I'm still fairly ignorant about the OS X extensions. I don't think this suggestion could cause any serious issues, but I can't guarantee that, so do this at your own risk!


    MacBook Pro (Retina, Mid 2012), OS X Mountain Lion (10.8.1), iPhone 4
  • Andreas Amann Level 5 Level 5 (7,815 points)
    Currently Being Moderated
    Oct 4, 2012 11:09 AM (in response to carnecro)

    carnecro wrote:

     

    You can remove the cookie directly in your account (`rm Library/Cookies/com.apple.appstore.plist`), when AppStore starts new cookie will be created. I think it's one of many hints in this thread and it does not work for me

     

    I tried deleting the plist too and it didn't work for me either - while the AppStore created a new com.apple.appstore.plist it was completely empty so it didn't work. Creating the file form another account and copying over worked (as that cookie is not corrupt/empty) - give it a try…

     

    Andreas

  • afiszone Calculating status...
    Currently Being Moderated
    Oct 4, 2012 11:12 AM (in response to unixy_goodness)

    Hello .. , i'm fix this, i'm upgrade my macbook pro to Mountain Lion 10.8.2, and try this http://www.computersnyou.com/2012/09/an-unknown-error-has-occurred-app-store.htm l

  • Andreas Amann Level 5 Level 5 (7,815 points)
    Currently Being Moderated
    Oct 4, 2012 11:19 AM (in response to afiszone)

    I would definitely stay away from that solution - messing with boot.plist is not a good idea and could get you in serious trouble!

     

    Andreas

  • afiszone Calculating status...
    Currently Being Moderated
    Oct 4, 2012 11:24 AM (in response to Andreas Amann)

    This tutorial original for hackintos, but work for me on my macbook pro. .  backup your boot.plist before your use this tutorial, if you get kernel panic, you can restore this from ubuntu live cd.

  • James Liang @ Taipei Calculating status...
    Currently Being Moderated
    Oct 10, 2012 12:39 AM (in response to mohd hatta)

    I try mohd hatta's suggestion below and it works for me now.

    "navigate to Library/Preferences/SystemConfiguration and then delete NetworkInterfaces.plist

    then restart ur mac, setting ur network and sign in app store"

    Xie Xie to mohd hatta ~~ (Thanks in Mandarin [Chinese] to mohd hatta) James Liang from Taiwan

  • wagaya Level 1 Level 1 (0 points)
    Currently Being Moderated
    Oct 10, 2012 1:07 AM (in response to James Liang @ Taipei)

    I'm glad that that solution seems to work for many people!

     

    Unfortunately, it does nothing for me. Still locked out of the App Store (one one user account; not on other accounts).

  • savagematt Calculating status...
    Currently Being Moderated
    Oct 12, 2012 10:17 AM (in response to mohd hatta)

    Thank you mohd hatta - this worked for me!

  • zphelj Calculating status...
    Currently Being Moderated
    Oct 15, 2012 3:48 PM (in response to OlofMork)

    Thanks to all for their contributions. Unfortunately even the 'create a dummy account' option isn't working for me!

     

    Pure speculation but I have a suspicion this is indeed tied into the network plist for some kind of newly rolled out copyright protection scheme that relies on the built in en0 MAC Address. I had a similar issue with Silverlight on the Mac I have with this problem, which is somewhat unusual in that the built in en0 is burned out and can't be created. So anything that relies on en0 being there dies a painful death.

  • wagaya Level 1 Level 1 (0 points)
    Currently Being Moderated
    Oct 15, 2012 4:06 PM (in response to zphelj)

    Here's what mystifies me, though: If the bug does lie in a system-wide issue like the device's en0 MAC address, then why would App Store sign-in for a given Apple ID fail for one user account on the device, yet work fine for another user account on the same device?

     

    That's my situation, which makes me think that the issue must lie in settings (Preferences, etc.) for the user account that can't sign in. Although my attempts to follow every suggestion and delete all possible offenders from the account's Library (and network.plist, etc.) is having no success.

     

    (To clarify the situation: My main user account on my iMac has no trouble using my Apple ID for iCloud and other purposes, but simply cannot sign in to the App Store with that Apple ID. Meanwhile, another user account on my iMac can use that same Apple ID for App Store login, with no problem.)

     

    Thus, I'm still looking for a user-specific issue causing the problem. No luck so far... : (

     

    Strange!

  • dillera Calculating status...
    Currently Being Moderated
    Oct 23, 2012 8:58 PM (in response to OlofMork)

    Hello: I experienced the same issue, after re-installing ML on a MBA that had previously had Lion and then been upgraded.

     

    No matter what I did (and I followed all the tips in this thread and found on other sites) I still had that annoying error, however I didn't have the error on a differnet user acct on my same Mac.

     

    Here is how I resolved it.

     

    Since I had created the 2nd user, i had done nothing with that user _except_ test the App Store, using my original apple ID. It worked fine.

     

    Then I tarred up the entire Library folder for that user into tmp, something like this:

     

    2nd user$ tar cvf /tmp/2nd-Library.tar Library

     

    Then I switched accts back to my primary user on the mac, the one that would not let me sign in to the App Store.

     

    First, i backed up my existing Library (I used a 2nd drive, you can back it up wherever)

     

    1st user$ rsync -avE Library /Volumes/DRIVE2/Library-Backup

     

    Once that was done, I extracted the good Library tarball OVER my Library, and it would only replace files that existed, and fix whatever broken files were in there.

     

    1st user$ tar xvf /tmp/2nd-Library.tar Library

     

    I immediately changed ownership back to myself, then I replaced some things I know had nothing to do with the App store and I needed:

     

    1st user$ sudo chown -R MYUSERNAME:staff Library/


    1st user$ cp -rpf /Volumes/DRIVE2/Library-Backup/Application\ Support/AddressBook/* Library/Application\ Support/AddressBook/


    1st user$ cp -rpf /Volumes/DRIVE2/Library-Backup/Keychains/* Library/Keychains/


    1st user$ cp -rpf /Volumes/DRIVE2/Library-Backup/* Library/Calendars/

     

     

    Then I ran App Store, and was able to sign-in, purchase and install apps.

  • anime_girl2015 Calculating status...
    Currently Being Moderated
    Oct 24, 2012 11:34 AM (in response to mohd hatta)

    It worked!!!!!! thank you sooo much!!!!! XD

  • 90studio Calculating status...
    Currently Being Moderated
    Oct 24, 2012 9:25 PM (in response to mohd hatta)

    I had the same problem, couldn't sign into the app store - login worked for iTunes though: I went to Library/Preferences/SystemConfiguration and then deleted 'NetworkInterfaces.plist', restarted my computer and voila, I could sign in to the app store on my account.

     

    Thank you Mohd Hatta for this!

  • zphelj Level 1 Level 1 (0 points)
    Currently Being Moderated
    Oct 25, 2012 6:27 AM (in response to wagaya)

    I agree it's strange though I'm thinking we have an uncaught exception that's tossed all the way to the top level which is "unknown error" and that means we could easily have multiple issues covered here

     

    Supporting: The various fixes posted are certainly working for some, while none of them have been effective for myself and others. This suggests it's possibly different core issues that all manifest with "unknown error". 

1 ... 3 4 5 6 7 ... 12 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (11)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.