New installs Crashing from MacOS App store in High Sierra

[vivek28]

Hello,

I have clean installed the MacOS High Sierra on my MBP 13 2010. I have reinstalled 2-3 times using new official HS setup.

Everything is working great except i cannot run any apps installed from Mac App store. 3rd party apps are running fine with dmg setups.

Adblock, Speedtest, Blackmagic disk etc. all are crashing on startup of apps. All apps versions are compatible with High sierra though.

I have tried resetting the app store caches also through terminal.

Pls help.

 

[ecliptic27]

I'm having the exact same problem on my late 2013 iMac. Have already reinstalled High Sierra, no change. Apps from third parties run well, but anything from the Mac App Store produces the error vivek28 shared above.

Any help would be appreciated, thanks.

 

[vivek28]

@ecliptic27 Many users are facing the same issue around the globe.

There is another thread that i checked in another HighSierra section of forums. I have posted in that too.. but no solution as yet.

Unable to open applications downloaded from the AppStore

I’m on a Mac Pro 5,1 and freshly installed High Sierra. For some reason I can’t open ANY application downloaded from the AppStore. Sometimes I can’t even download the app, sometimes it allows me to at least download it after I try it over and over again. Some people I already asked suggested...

forums.macrumors.com

 

[cocoflan]

Found solution for problem, force install macos high sierra with HFS+, then you don't get the errors.

First install an older version of MACOS lower than High sierra, and then force a command on the high sierra installer.

Is It Possible Not to Convert to APFS When Upgrading to High Sierra?

There are a couple of strategies you can use to prevent the upgrade to APFS and retain the older HFS+ formatting:

eshop.macsales.com

There is a serious problem with APFS on systems from 2012, when using HFS+ no problems using the Macos APP store, only when using APFS, and High Sierra converts the disk automatic so the command makes conversion impossible, and uses HFS+.

Greetings

 

[vivek28]

Found solution for problem, force install macos high sierra with HFS+, then you don't get the errors.

First install an older version of MACOS lower than High sierra, and then force a command on the high sierra installer.

Is It Possible Not to Convert to APFS When Upgrading to High Sierra?

There are a couple of strategies you can use to prevent the upgrade to APFS and retain the older HFS+ formatting:

eshop.macsales.com

There is a serious problem with APFS on systems from 2012, when using HFS+ no problems using the Macos APP store, only when using APFS, and High Sierra converts the disk automatic so the command makes conversion impossible, and uses HFS+.

Greetings

not sure.. but using high sierra with APFS since its release.. but problems did occur only now. And it is happening since mid Nov onwards.. with big sur release, which might be totally unrelated.

Is support for high sierra being dropped magically now ehh lol ? It is still a fast and potent OS on older macs.

 

[cocoflan]

It was indeed not correct my explanation, the only way is to use Sierra instead of Highsierra, So I think it is a problem with the apfs filesystem autoconversion in combination with the Highsierra operating system, works perfectly now on Sierra, the problem occurred on an Imac from Mid 2010 and is solved now.

 

[pedro1970]

I have the problem, too. On my MBP (mid 2012) i did made all updates up to Catalina. Due to some compatibility issues (dropped 32Bit, Music App, ...) i decided to go back to my favourite macOS on this machine, High Sierra. So as always i made a complete clone of the SSD with CCC, a bootable USB-Stick with High Sierra from the App Store.
So i got an absolute fresh clean install. The first thing was to re-install my apps from the App Store. I got the message that downloading is not possible, should try the bought option (i am in germany, don’t know the english buttons exactly).
When i managed to download an app (no matter if new or already bought), i can’t launch it. I get the unexpected error with: EXC_CRASH (Code Signature Invalid) in the log.

Then i re-installed the macOS from the ground. This time with formatting with APFS instead of Mac Extended - with the same result: everything is working fine, except the App Store.

Because of the „Code Signature Invalid” message in the log i think it’s Apple’s fault. I did write them an email, hoping to get an answer soon. Please, everyone who have the same problem, also ask Apple for help.

I am very frustrated that i have to interrupt my productivity for days because of this issue and just can’t use my payed apps right now.

 

[cocoflan]

All is still working great after some days using Sierra (not High Sierra) as temporary solution, so there must be a problem with the new filesystem and the newer Macos versions in combination with the 2010 hardware. But on Sierra (Not High Sierra) you can install almost all the same apps like on Macos High sierra and Catalina from the appstore.

Hope Apple will solve that problem. So upgrading and using the new filesystem will work in combination with the appstore.

A temporary solution maybe for the moment!

 

[vivek28]

All is still working great after some days using Sierra (not High Sierra) as temporary solution, so there must be a problem with the new filesystem and the newer Macos versions in combination with the 2010 hardware. But on Sierra (Not High Sierra) you can install almost all the same apps like on Macos High sierra and Catalina from the appstore.

Hope Apple will solve that problem. So upgrading and using the new filesystem will work in combination with the appstore.

A temporary solution maybe for the moment!

is Sierra faster than High Sierra ? boot, apps load.. and general performance

 

[alansoge]

I've been experiencing the same issue but i have researching and I found that it might affect only to sandboxed apps (those including from App Store or downloaded from internet that use sandboxing as App Store).

I also tried reinstalling High Sierra 6 times, 1 from usb, 1 from internet recovery and the others only change using HFS+ or APFS and I get the same error, APPS ARE CRASHING. I don't know what to do.

(Sorry for my bad English, I'm learning yet) I'm very concerned.
Below is an example of WhatsApp, but it happen the same with sandboxed apps.



Process: WhatsApp [4546]
Path: /Applications/WhatsApp.app/Contents/MacOS/WhatsApp
Identifier: desktop.WhatsApp
Version: 2.2047.10 (2.2047.10)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: WhatsApp [4546]
User ID: 501

Date/Time: 2020-11-29 01:31:40.323 -0600
OS Version: Mac OS X 10.13.6 (17G14033)
Report Version: 12
Anonymous UUID: E7BDB22B-CCC0-E67A-5734-CC745063D284


Time Awake Since Boot: 1000 seconds

System Integrity Protection: disabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Illegal instruction: 4
Termination Reason: Namespace SIGNAL, Code 0x4
Terminating Process: exc handler [0]

Application Specific Information:
dyld: launch, running initializers
/usr/lib/libSystem.B.dylib
Sandbox registration failed: The code signature is not valid: The operation couldn’t be completed. (OSStatus error -2147409652.)

Application Specific Signatures:
Registration error: The code signature is not valid: The operation couldn’t b

 

[pikturhaus]

Found solution for problem, force install macos high sierra with HFS+, then you don't get the errors.

First install an older version of MACOS lower than High sierra, and then force a command on the high sierra installer.

Is It Possible Not to Convert to APFS When Upgrading to High Sierra?

There are a couple of strategies you can use to prevent the upgrade to APFS and retain the older HFS+ formatting:

eshop.macsales.com

There is a serious problem with APFS on systems from 2012, when using HFS+ no problems using the Macos APP store, only when using APFS, and High Sierra converts the disk automatic so the command makes conversion impossible, and uses HFS+.

Greetings

did that. but when i upgraded to high sierra the disk was formated by the software itself to APFS. What do u mean by "force a command on the high sierra installer"? how could i do that?

 

[pikturhaus]

i tried also to restore with time machine (i had a backup with high sierra on HFS+) . this is because time machine can't use APFS formatting (yet). no result. after the restore, the disk on my mac was, again, formatted in APFS. But wait! here is the mistery: for about 15-20minutes everything was good—the apps did work. after that.. all the apps downloaded with mac app store just stopped working...

 

[alansoge]

I found a solution (thanks to @DocteurQui ). We only need to delete file “valid.sqlite3” on /Library/Keychains/clrs.

And now, if we open an app, it works. In this case I don’t know if this is a permanent or temporary solution but meanwhile we can use apps from AppStore.

 

[3ingot]

Noticed problem 12/1/20 and assumed it was my lack of ability or archaic hardware. But it seems issue arose in Nov. Three calls to Apple provided no insight…

Have a Late 2009 iMac with original HD running El Capitan 10.11.6. Just swapped optical drive for new WD 1TB SSD. Installed High Sierra 10.13.6 and Security Updates 2020-005, -006. Apple and 3rd party apps downloaded from App Store won’t launch while apps installed with OS or copied from HD run fine.

Tried multiple installs from USB boot disk and “Install macOS High Sierra” app from internal HD. Also tried installing over HFS+, upgrading over El Capitan, launching apps prior to installing security updates, signing out of iCloud on all apps and removing iMac from Apple ID prior to installing High Sierra. Currently have a clean install of El Capitan on SSD and App Store apps launch without issue.

BUT…also own Mid-2010 iMac running High Sierra with SSD formatted APFS. Security updates are current and it runs same apps that crash on Late 2009 iMac. Today downloaded Affinity Publisher through App Store. No problem. Apple and 3rd party apps previously installed through App Store are fine as well. Aside from processor and hardware differences between the two, the non-crashing Mac runs High Sierra off an SSD installed in the HD bay while the crashing Mac has its original HD running El Capitan and an SSD running High Sierra. (El Cap on both = no problem.) Several others mention having both SSD and HD. Is anyone running High Sierra with apps crashing on systems with HD only?

 

[DocteurQui]

I found a solution (thanks to @DocteurQui ). We only need to delete file “valid.sqlite3” on /Library/Keychains/clrs.

And now, if we open an app, it works. In this case I don’t know if this is a permanent or temporary solution but meanwhile we can use apps from AppStore.

The problematic file come back after a while, I guess a script that delete it automatically would work but I have no idea as how to do it !

Several others mention having both SSD and HD. Is anyone running High Sierra with apps crashing on systems with HD only?

I only have the original HD and it crashes (before I delete the valid.sqlite3 file).

 

[3ingot]

Yes, thanks to @DocteurQui. For me the file seemed to be rebuilt (and apps wouldn't launch) at reboot. But only when connected to the internet. (See reply to your comment at Unable to open applications downloaded from the AppStore). When not connected to internet at reboot apps continue to launch.

 

[3ingot]

I only have the original HD and it crashes (before I delete the valid.sqlite3 file).

Thanks. There are 5 Macs here, 3 of which run High Sierra. It's been installed on 2 since 2019 but I just loaded it onto my Mac (on a second drive) this week. Mine seems to be the only one with App Store app problems.

 

[pikturhaus]

My mac is running Sierra right now..because I was too tired to try other options (I had already reinstalled macOS about 7 times), on the new SSD (kingston by the way) which I put in. Previously I had High Sierra (10.13.6 I guess) with all the security updates 005, 006 running on my HDD (the original one—seagate 1TB)

what is apple doing???

 

[3ingot]

The problematic file come back after a while, I guess a script that delete it automatically would work but I have no idea as how to do it !

Might have stumbled on a longer-term workaround.

Replaced "valid.sqlite3" with file from an iMac running High Sierra that has no App Store issues. Tested for a while and App Store apps have been working fine with no need to continually delete the generated file. Since High Sierra is new to this iMac I have no backup of "valid.sqlite3" which is why I used one from another iMac.

One last comment: my SSD had a fresh High Sierra install but not Security Update 2020-005 or -006. I wanted to confirm that the security updates weren't the cause of crashing apps. They weren't. (Just passing along a word of caution since my App Store currently doesn't show those updates anymore. Not sure why. They may show up later. It's happened before.)

 

[pikturhaus]

Might have stumbled on a longer-term workaround.

Replaced "valid.sqlite3" with file from an iMac running High Sierra that has no App Store issues. Tested for a while and App Store apps have been working fine with no need to continually delete the generated file. Since High Sierra is new to this iMac I have no backup of "valid.sqlite3" which is why I used one from another iMac.

One last comment: my SSD had a fresh High Sierra install but not Security Update 2020-005 or -006. I wanted to confirm that the security updates weren't the cause of crashing apps. They weren't. (Just passing along a word of caution since my App Store currently doesn't show those updates anymore. Not sure why. They may show up later. It's happened before.)

So, the best option is to replace the file “valid.sqlite3” located in /Library/Keychains/clrs , with the same file from another Mac running High Sierra on HFS+ with no Mac App Store problems. That’s it?

 

[Trystero]

There is a very long discussion in the Apple Forum. It seems you need to get two files from a backup prior to the last security update:
/System/Library/Security/Certificates.bundle
/Library/Keychains/crls/valid.sqlite3

Read the message of FrancoisQC, december 2, 4:42 PM :

App Store apps do not install properly on… - Apple Community

discussions.apple.com

 

[DocteurQui]

There is a very long discussion in the Apple Forum. It seems you need to get two files from a backup prior to the last security update:
/System/Library/Security/Certificates.bundle
/Library/Keychains/crls/valid.sqlite3

Read the message of FrancoisQC, december 2, 4:42 PM :

App Store apps do not install properly on… - Apple Community

discussions.apple.com

I'm going to try this tomorrow, thanks !

 

[pikturhaus]

I'm going to try this tomorrow, thanks !

Good Luck! and tell us if it works, please!

 

[3ingot]

So, the best option is to replace the file “valid.sqlite3” located in /Library/Keychains/clrs , with the same file from another Mac running High Sierra on HFS+ with no Mac App Store problems. That’s it?

Seems so, for now.

See Dec 6, 2020 3:07 AM post from johnno_uk in Apple Communities thread App Store apps do not install properly on a fresh install of High Sierra on internal SSD or HDD, referenced by Trystero, paulcons & others. It's way back on page 25.

Also, from what I've read it shouldn't matter if source file is from HDD or SSD, APFS or HFS+. I copied mine from an SSD formatted as APFS. (FWIW my fix has been working for ~ a day through restarts, switching users, and logging back-n-forth between a second disk running El Capitan.)

DocteurQui, you may need to only replace "valid.sqlite3" and not Certificates.bundle. (See post by johnno_uk Dec 5, 2020 11:48 AM on page 25.)

 

[3ingot]

FWIW…as discussed, after fresh HS install App Store apps crashed. Replaced "valid.sqlite3" with file from iMac running HS since Dec 2019 which appears to have resolve crashes. This was prior to installing Security Update 2020-005, which has just been done. I wondered if -005 would break it but App Store apps still launch, etc. Some have suggested that security updates were the cause but not in my experience.