After upgrade to MacOS Mojave, I cannot login or connect to App Store.

We had exactly the same problem after we upgraded our 3 iMacs at work- I tried all the solutions mentioned here but nothing fixed the problem. Signing in with another admin account didn't solve anything, tried to delete all the files mentioned in another thread- nothing changed.. We are all connected over ethernet and this morning I disconnected the ethernet and opened up a personal HotsSpot on my iPhone- and now the App Store is back to life..! But as soon as I disconnect the WiFi connection, go back to ethernet and close the App Store- same as before. But at least we found a solution for now. Maybe that will help someone...

So this is a network related issue with the App Store and network port configuration. Funny that so many folks can replicate the issue but we have yet to hear from  Support on a quick fix. Does anyone know what ports the App Store uses when it's connects to Apple's servers?

Stefanspk wrote:

We had exactly the same problem after we upWe are all connected over ethernet and this morning I disconnected the ethernet and opened up a personal HotsSpot on my iPhone- and now the App Store is back to life..!

Tried this immediately just seeing your post - no luck unfortunately. Same behavior with personal hotspot as with ethernet and wifi.

You might want to check any network filters you have on your wired network. I had a similar problem and was able to determine that my third party network filter (Little Snitch) was not reading the code signature for the app store correctly. A subsequent update to the third party network filter solved my problem.

b33rg33k wrote:

So this is a network related issue with the App Store and network port configuration. Funny that so many folks can replicate the issue but we have yet to hear from  Support on a quick fix. Does anyone know what ports the App Store uses when it's connects to Apple's servers?

Yes, I've looked at it. The app store mostly uses 443/tcp, but I don't believe that's the issue. In my case there is no actual network connection attempted that I've been able to detect when signin fails.

Like some of the posters a few pages back I suspect an issue with certificates that are causing the SSL connection to fail before a TCP packet is even sent, but have not had any luck figuring out which exactly and where.

Exxplora2 wrote:

You might want to check any network filters you have on your wired network. I had a similar problem and was able to determine that my third party network filter (Little Snitch) was not reading the code signature for the app store correctly. A subsequent update to the third party network filter solved my problem.

Tried that here too - unfortunately no luck with with the Little Snitch update nor with disabling LS.

I can copy the Security file but I stupid out when it came to the other steps.

I don't know where to go to begin the cd part.

Also, is that command performed on the original account or the alias?

Anyway, I here declare my stupidity.

Open Terminal (Applications/Utilities) and cut and paste each line, one at a time, into it. Hit Enter. If you're prompted for your password, it's asking for the password you log on to your Mac with, which should have Administrator access.

After you follow the directions in the first part of BocaBoy's post open the terminal located in Applications/Utilities and type or copy and paste each line and press enter after each copy and paste. So you will have copied and pasted three times. Now after the first line is copied and pasted the terminal will ask for your password (the one you use to enter Mac OS) after that it is just copy paste and then when the last line is entered and enter is pressed reboot and all should be working. Below is details.

sudo ditto -ck "Trust Settings" TrustSettingsBackup.zip (Then press enter)

Now enter password

cd "/Library/Security/Trust Settings" (Then press enter)

sudo rm *.plist" (Then Press enter)

Now reboot

Prarrori1, The first line gives you Administrator rights to create a Zip file of Trust Settings, then creates the file. The second command changes the directory (cd) to Library/Security/Trust Settings. The third command gives you Administrator rights to remove any file ending in plist. These are preference files and are regenerated when they are missing. The error appears to be in that file. Apple is asking for it to be deleted so that it can be regenerated with fresh content.

Use Terminal to cut and paste these commands into, one at a time, using Enter after each one. If your password is needed, it will prompt you for it.

Lastly, if you're uncomfortable working at the system level, DON'T DO THIS. Many people in this forum and on this thread are comfortable using Terminal. They also, presumably, have the know-how to recover if they make a mistake. If you're not one of them, I repeat, DON'T DO THIS.

Now that Apple engineering has identified and acknowledged the problem, it will show up in a future release, maybe as early as 10.14.1.

Ohhhhh k. Still out. Every time I posted a line and then hit Enter, it would just repeat my name plus MacBook Pro.

I do appreciate all you that tried to help me. This failure by me is not on any of you. It's all mine.

OK lets do it this way.

1. After the first line was entered, did the line below that ask for password? If yes great and enter next line there will be no more prompts other than your MacBook Pro line. Then enter the next line also no prompts other than MacBook Pro. If all lines entered reboot. All should work. If you didn't get the prompt for password get back to us.

this was really helpful, both app\book stores are back to normal. appreciate that! just wondering apple allows this issue for such a long time with no official response 😟 , also any impact when remove this file?

macnewED

The plist files that are removed will be regenerated the next time they're required by an application. There's either some sort of corruption or contradictory line of code in those files that was causing the problem.

Apple prioritizes their focus first on items that crash the system or cause kernel panics, then start down the list from there. I've been beta testing Mojave for months, and this problem has been there since I started. It doesn't appear to be too wide spread since, on the developers forum, I was the only one reporting the problem. Once Mojave went into wider release, it started to affect more people and hence it got their attention.

Im giving up. This is what happens to me whenever I hit enter. Also when i enter password it doesn't take i.e. not posted

Last login: Wed Oct 3 14:23:55 on console

Richard-MacBook-Pro:~ richard$ cd "/Library/Security"

Richard-MacBook-Pro:Security richard$ sudo ditto -ck "Trust Settings" TrustSettingsBackup.zip

Password:

ditto: no files for PKZip archive

Richard-MacBook-Pro:Security richard$ cd "/Library/Security/Trust Settings"

Richard-MacBook-Pro:Trust Settings richard$ sudo rm *.plist

rm: *.plist: No such file or directory

Richard-MacBook-Pro:Trust Settings richard$

Richard-MacBook-Pro:Trust Settings richard$