An unknown error has occurred app store

An unknown error has occurred


This message An unknown error has occurred when i try login to APPSTORE in my MacBookAir.'

MacBook Air, OS X Mountain Lion (10.8.1), Problem to log in to app store

Posted on Aug 31, 2012 3:45 AM

Reply
Question marked as Top-ranking reply

Posted on Oct 4, 2012 10:25 AM

wagaya wrote:


Really bizarre. Hearing some people suggest that it's a problem on Apple's end is discouraging, as it suggests anything else I try may automatically fail. Yet if I can use the App Store from another user account, that suggests there has to be something lurking in my main account's Library (probably) that's causing the problem...


After running around in circles trying to get this resolved for me I finally found a (fairly easy) solution - the key point here is that the AppStore works just fine form another user account on the same computer (using the same AppleID) so it has to be something in ~/Library rather than /Library (thus ruling out the NetworkInterfaces.plist fix - which I tried and which didn't work for me).


Here is a step-by-step of what worked for me:


  1. Create a new user account - let's name it "Test" - I did not make this an administrator account
  2. Log into that new user account (skipping the AppleID/iCloud screen)
  3. Select "Software Update…" from the Apple menu - you will be asked to enter an administrator name and password in or to check for system updates - just provide your normal (admin-enabled) user name and password
  4. If you have any updates available, click "Update All" and log into the AppStore with your normal AppleID/password (this should work since you are in a new user account)
    (If you don't have any updates available, I assume that you can also log in using the menu item in the Store menu of the AppStore application though I have not tried that)
  5. As soon as the download starts, you can quite the AppStore application
  6. Log out of your test account and back into your normal account
  7. Open /Applications/Utilies/Terminal
  8. Type the following command:
    sudo cp /Users/test/Library/Cookies/com.apple.appstore.plist Library/Cookies/
  9. Open the AppStore again and you should be able to log back in


What does this do? It seems that the com.apple.appstore.plist file in your normal user account has become corrupted - we use a new account and create a new one (which is interchangebale since we use the same AppleID) and move that one back to the main account with the corrupt file.


AndreasUser uploaded file

198 replies
Question marked as Top-ranking reply

Oct 4, 2012 10:25 AM in response to wagaya

wagaya wrote:


Really bizarre. Hearing some people suggest that it's a problem on Apple's end is discouraging, as it suggests anything else I try may automatically fail. Yet if I can use the App Store from another user account, that suggests there has to be something lurking in my main account's Library (probably) that's causing the problem...


After running around in circles trying to get this resolved for me I finally found a (fairly easy) solution - the key point here is that the AppStore works just fine form another user account on the same computer (using the same AppleID) so it has to be something in ~/Library rather than /Library (thus ruling out the NetworkInterfaces.plist fix - which I tried and which didn't work for me).


Here is a step-by-step of what worked for me:


  1. Create a new user account - let's name it "Test" - I did not make this an administrator account
  2. Log into that new user account (skipping the AppleID/iCloud screen)
  3. Select "Software Update…" from the Apple menu - you will be asked to enter an administrator name and password in or to check for system updates - just provide your normal (admin-enabled) user name and password
  4. If you have any updates available, click "Update All" and log into the AppStore with your normal AppleID/password (this should work since you are in a new user account)
    (If you don't have any updates available, I assume that you can also log in using the menu item in the Store menu of the AppStore application though I have not tried that)
  5. As soon as the download starts, you can quite the AppStore application
  6. Log out of your test account and back into your normal account
  7. Open /Applications/Utilies/Terminal
  8. Type the following command:
    sudo cp /Users/test/Library/Cookies/com.apple.appstore.plist Library/Cookies/
  9. Open the AppStore again and you should be able to log back in


What does this do? It seems that the com.apple.appstore.plist file in your normal user account has become corrupted - we use a new account and create a new one (which is interchangebale since we use the same AppleID) and move that one back to the main account with the corrupt file.


AndreasUser uploaded file

Jan 24, 2013 12:45 PM in response to dillera

This works for me. I found I only needed to copy Caches (and iTunes, which only contains an empty directory) from the test account, not the entire Library.

dillera wrote:


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.

May 20, 2013 5:05 AM in response to steforster

This worked for me (after trying several others). Thanks



.. this is definately an issue with pushing the request for the End User to accept new changes in Apples' T&C's via OSX. The fix is: Open AppStore, select 'Store' and then 'Signout'. Then select 'Store' but select 'Create Account.', then 'Continue' and tick 'I've Read ...' this will give you the opportunity to 'Accept' the T&C's - 'Cancel' the new registration and log back in with your orignial Apple I.D.

Sep 20, 2012 10:26 PM in response to OlofMork

As I just posted elsewhere, I discovered what was preventing me from doing updates/installs from the App Store was a permission problem that occured when I did a SetupAssistant transfer to my brand-new MBP. This permission issue did not get fixed by Disk Utility's "repair permissions."


Opening up the terminal, and doing the following worked for me:


cd ~

chmod 755 Library/Cookies


It may be desirable to change the permissions on all of the Cookie files, if the permissions on the individual files got messed up somehow. In that case, you would type:


cd ~

chmod -R 755 Library/Cookies


I don't know if this is the cause of other people's issue, but it solved mine. Good luck!

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!

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.

Jan 2, 2013 4:12 PM in response to Andreas Amann

Here is a step-by-step of what worked for me:


  1. Create a new user account - let's name it "Test" - I did not make this an administrator account
  2. Log into that new user account (skipping the AppleID/iCloud screen)
  3. Select "Software Update…" from the Apple menu - you will be asked to enter an administrator name and password in or to check for system updates - just provide your normal (admin-enabled) user name and password
  4. If you have any updates available, click "Update All" and log into the AppStore with your normal AppleID/password (this should work since you are in a new user account)
    (If you don't have any updates available, I assume that you can also log in using the menu item in the Store menu of the AppStore application though I have not tried that)
  5. As soon as the download starts, you can quite the AppStore application
  6. Log out of your test account and back into your normal account
  7. Open /Applications/Utilies/Terminal
  8. Type the following command:
    sudo cp /Users/test/Library/Cookies/com.apple.appstore.plist Library/Cookies/
  9. Open the AppStore again and you should be able to log back in

this worked for me, only addition is I had to log in as super user / root in order to copy the file, and then chown (change owner) the file to my user name

Jan 15, 2013 10:50 AM in response to OlofMork

.. this is definately an issue with pushing the request for the End User to accept new changes in Apples' T&C's via OSX. The fix is: Open AppStore, select 'Store' and then 'Signout'. Then select 'Store' but select 'Create Account.', then 'Continue' and tick 'I've Read ...' this will give you the opportunity to 'Accept' the T&C's - 'Cancel' the new registration and log back in with your orignial Apple I.D.

Jan 22, 2013 2:26 AM in response to steforster

steforester's solution worked brilliantly for me, and by far the least technical.


.. this is definately an issue with pushing the request for the End User to accept new changes in Apples' T&C's via OSX. The fix is: Open AppStore, select 'Store' and then 'Signout'. Then select 'Store' but select 'Create Account.', then 'Continue' and tick 'I've Read ...' this will give you the opportunity to 'Accept' the T&C's - 'Cancel' the new registration and log back in with your orignial Apple I.D.

Feb 21, 2013 6:13 AM in response to samuelbarber19

samuelbarber19 wrote:


Hi,


I had this problem and the fix was simple for me. Change the country / region from your country to the USA (if you live in the USA change the region to the United Kingdom) and then look at a specific app (i.e. go to more than just the main page on the mac app store), once you have done this change the region back to your actual country, this will then force the Mac App Store to get you to sign back in. This should then fix the problem.


Wow, this worked! Thanks a lot. Changed country, viewed an app or two, changed country back and signed in and it works perfect with my main account!

Feb 27, 2013 4:29 AM in response to steforster

After trying four other solutions only the following worked for me. Thanks!

steforster wrote:


.. this is definately an issue with pushing the request for the End User to accept new changes in Apples' T&C's via OSX. The fix is: Open AppStore, select 'Store' and then 'Signout'. Then select 'Store' but select 'Create Account.', then 'Continue' and tick 'I've Read ...' this will give you the opportunity to 'Accept' the T&C's - 'Cancel' the new registration and log back in with your orignial Apple I.D.

Apr 1, 2013 2:07 PM in response to machsx

This worked for me as well.


steforster wrote:


.. this is definately an issue with pushing the request for the End User to accept new changes in Apples' T&C's via OSX. The fix is: Open AppStore, select 'Store' and then 'Signout'. Then select 'Store' but select 'Create Account.', then 'Continue' and tick 'I've Read ...' this will give you the opportunity to 'Accept' the T&C's - 'Cancel' the new registration and log back in with your orignial Apple I.D.

Apr 21, 2013 4:25 PM in response to OlofMork

it seems that some of the apps have got a module contained in a folder named, “_MASReceipt” this module is located in the programme itself so you will have to look for it inside the app.

apparently this is the cause of all this mess, when you intend to login the appstore the module closes the connection thats why in some computers the appstore works and some others it doesnt.

check this app to locate the related file..

http://apps.tempel.org/FindAnyFile/

read this link wil xplain the whole enchilada..

http://apple.stackexchange.com/questions/53648/mac-app-store-how-to-check-which- account-was-used-to-buy-app

To make the AppStore forget the old credentials with which an app was downloaded, you must remove the

_MASReceipt
directory in the app itself.

  1. Launch 'Find Any File' and search for: _MASReceipt
  2. Go through each result that you think could be the culprit, copy the receipt to your desktop as a backup, and after that delete the receipt inside _MASReceipt folder.
  3. Open MAS and let it scan for software update. If it's still showing the wrong ID, it means that you've deleted the wrong receipt. Restore the receipt backup from your desktop to it's previous location.
  4. Repeat the process until you've found the problem receipt



To make the AppStore forget the old credentials with which an app was downloaded, you must remove the

_MASReceipt
directory in the app itself.

To do this:

  1. Open Finder and navigate to Applications,
  2. Ctrl+Click the application you want to redownload and choose "Show Package Contents",
  3. Expand the Contents directory and click _MASReceipt to select it,
  4. Type Command+Delete to delete the directory permanently---you will be prompted for your credentials since this is a protected file.

Quit and restart AppStore, then find the application you want to update. The button should now say "Free" or "Install" instead of "Update". Clicking it will update your app to the latest version, doing so as the currently logged-in Apple user.


i hope this help

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

An unknown error has occurred app store

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.