MP All Models Pages & Numbers app crashing with "Namespace CODESIGNING" error?

[Loa]

Hello,

I'm on 10.13.6 with Pages 8.1, and I've never had any trouble. This morning though, I can't launch either Pages or Numbers. I haven't updated anything.

All other apps work normally.

Any help would be really appreciated as I can't work at all right now.

=========================================
Process: Pages [1020]
Path: /Volumes/*/Pages.app/Contents/MacOS/Pages
Identifier: com.apple.iWork.Pages
Version: ???
Build Info: Pages-6369000000000000~2
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Pages [1020]
User ID: 501

PlugIn Path: (null)
PlugIn Identifier: (null)
PlugIn Version: ??? (551.5)

Date/Time: 2020-08-05 11:31:27.027 -0400
OS Version: Mac OS X 10.13.6 (17G8030)
Report Version: 12
Anonymous UUID:


Time Awake Since Boot: 1300 seconds

System Integrity Protection: enabled

Crashed Thread: 0

Exception Type: EXC_CRASH (Code Signature Invalid)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace CODESIGNING, Code 0x1

kernel messages:

VM Regions Near 0 (cr2):
-->
__TEXT 0000000102459000-000000010357d000 [ 17.1M] r-x/rwx SM=COW

Thread 0 Crashed:
0 ??? 0x000000010568a19c _dyld_start + 0

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000
rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x00007ffeed7a6be8
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
rip: 0x000000010568a19c rfl: 0x0000000000000200 cr2: 0x0000000000000000

Logical CPU: 0
Error Code: 0x00000000
Trap Number: 0


Binary Images:
0x102459000 - 0x10357cff7 +??? (6369) <26F0E529-C9BC-3387-8970-4E131B9F4CA8> (null)
0x105689000 - 0x1056d3acf +??? (551.5) <30B355CB-35BA-3112-AA76-4E46CD45F699> (null)

External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 941
thread_create: 0
thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=18.2M resident=0K(0%) swapped_out_or_unallocated=18.2M(100%)
Writable regions: Total=8668K written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8668K(100%)

VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
STACK GUARD 56.0M 2
Stack 8192K 2
__DATA 4164K 5
__LINKEDIT 832K 3
__TEXT 17.4M 3
shared memory 8K 3
=========== ======= =======
TOTAL 86.3M 12

 

[tommy chen]

apple has certifikat problems

 

[Loa]

Ok, and how can I fix this? The apps are working fine on my other computers.

 

[jharris9]

I upgraded my 2012 Mac Pro from El Capitan (10.11.) to High Sierra (10.13.6). Some of my apps failed to work, saying that they needed updating or they just wouldn’t open.

So I went to the Mac App store and looked at my suggested “Updates”. There were a dozen or so that it showed were in need of an update. Reasoning that my change to a more recent MacOS probably broke the apps, I clicked “Update All”. Apple’s Numbers and Keynote needed “drop back” updates. The latest Version for Numbers is 10.2 but it selected Version 6.1 for my MacOS High Sierra, since the latest version need 10.15, Catalina, to work.

When everything finished updating, every single one of them “quit unexpectedly” with the same mode of failure: “Code Signature Invalid… Termination Reason: Namespace CODESIGNING, Code 0x1”. I even downloaded some apps I’ve never used or had on any of my systems in the past, but they failed the same way. I got copies of some of the failed Apps from my backup drive and some of them worked, though most needed a proper install, so they showed a “Damaged” failure mode.

One of the failured Apps was “MacTracker”, which needed to go from Version 7.9.3 to 7.9.7. It worked in V.7.9.3 but not after updating from the App Store to 7.9.7. Luckily, it can be upgraded from within the App. The update to 7.9.7 from within the App, not from the App Store, is working just fine.

I see a pattern but not a solution. Anything I update from the Apple App Store, or even new Apps never Downloaded before, will fail with the same “Code Signature” failure.

I tried rebooting… a lot. I tried fixing permissions. I tried opening the Apps after booting in Safe Mode. I tried opening the Apps with no Internet connection (which showed that the failure is in the program and not coming from a rejection from Apple servers. I got a new SSD and made it my new system drive. The Apps always failed and the failure was always the same “CodeSigning”.

Anyone have this problem or know a solution?

I read about Apple’s failures with Security Certificates and even had some experience with it last year (horrible and completely preventable with just some care to detail). They also have a history, from 2016, of just this type of Code Signing failure in the past, so I am going to blame the serial criminal before looking to make my system the corrupt one.

Any lawyers who need work and would like to start a class action lawsuit? Apple doesn’t seem to notice customers, only potentially big cash penalties.

 

[Loa]

Thanks for the added info. In my case, only a full erase and restore from back-up "solved" the issue.

Loa

 

[jharris9]

I don't have a backup that works with my recent OS upgrade, so not possible for me. I guess I could drop back to older OS version backup. I just don't understand how this couldn't be an Apple problem that they could fix with some attention.

 

[cavenewt]

Today is November 23, 2020. Two days ago I upgraded a client's Yosemite system to High Sierra using a freshly downloaded Installer. Now every App Store app refuses to launch with a codesigning error. Apparently this is a long running problem. Is there any way around it? Yes, I've tried re-downloading and reinstalling the apps.

 

[cavenewt]

Today is November 23, 2020. Two days ago I upgraded a client's Yosemite system to High Sierra using a freshly downloaded Installer. Now every App Store app refuses to launch with a codesigning error. Apparently this is a long running problem. Is there any way around it? Yes, I've tried re-downloading and reinstalling the apps.

Two possible Terminal workarounds. No idea which to try! The entire thread is pretty informative.

• https://discussions.apple.com/thread/252037712?answerId=253962571022#253962571022
• https://discussions.apple.com/thread/252037712?answerId=252037712021#252037712021

 

[cavenewt]

Two possible Terminal workarounds. No idea which to try! The entire thread is pretty informative.

• https://discussions.apple.com/thread/252037712?answerId=253962571022#253962571022
• https://discussions.apple.com/thread/252037712?answerId=252037712021#252037712021

The previous solution did not stick across reboots for some people. There's a new one by the same poster that appears to work better:

> Hope this helps everyone:
>
> 1. Open a terminal
> 2. run the following command
>
> ```
> sudo rm -f /Library/Keychains/crls/valid.sqlite3
> ```
>
> I haven't tested, but I think a reboot is not even necessary. And this does survive a reboot.
>
> It looks like this file may be used by "trustd". So worse case scenario, this will **rebuid** trustd's cache, so that should not affect the security of your system.

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

discussions.apple.com

 

[cavenewt]

The previous solution did not stick across reboots for some people. There's a new one by the same poster that appears to work better:

> Hope this helps everyone:
>
> 1. Open a terminal
> 2. run the following command
>
> ```
> sudo rm -f /Library/Keychains/crls/valid.sqlite3
> ```
>
> I haven't tested, but I think a reboot is not even necessary. And this does survive a reboot.
>
> It looks like this file may be used by "trustd". So worse case scenario, this will **rebuid** trustd's cache, so that should not affect the security of your system.

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

discussions.apple.com

...or maybe not. https://discussions.apple.com/thread/252037712?answerId=253981263022#253981263022

The people on this thread seem to have a good chance of figuring out eventually. I hope.

 

[Loa]

One of the thing that's bugging me is that Apple is aware of such obscure problems like this one, and they know how to fix it.

(There's also the odd one where accepting the updating prompt for an iOS 14 device somehow prevents iMovie from exporting movies in 10.13.)

But they choose to remain silent. And us users must find the solution ourselves. Such a shame.

 

[Rapidecho]

The previous solution did not stick across reboots for some people. There's a new one by the same poster that appears to work better:

> Hope this helps everyone:
>
> 1. Open a terminal
> 2. run the following command
>
> ```
> sudo rm -f /Library/Keychains/crls/valid.sqlite3
> ```
>
> I haven't tested, but I think a reboot is not even necessary. And this does survive a reboot.
>
> It looks like this file may be used by "trustd". So worse case scenario, this will **rebuid** trustd's cache, so that should not affect the security of your system.

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

discussions.apple.com

Thanks !!! it's work for me
juste sudo rm -f /Library/Keychains/crls/valid.sqlite3
without reboot