Signal keeps crashing on MacOS after recent Sequoia update

[thomasdn]

Using a supported version?

• I have searched searched open and closed issues for duplicates.
• I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.

Overall summary

After my recent update of macOS to the Sequoia version, Signal worked initially but shortly after the macOS update, Signal received an update as well. After this update Signal crashes immediately when I try to start it.

I just get the "Signal quit unexpectedly" message and the option to send a crash report.

I am not sure what details in the crash report are safe to post here. I do not want to risk exposing any sensitive data like keys, etc. that might compromise my Signal security or that could be used to identify me.

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Incident Identifier: *********
CrashReporter Key:   ***********
Hardware Model:      Mac15,3
Process:             Signal [2907]
Path:                /Applications/Signal.app/Contents/MacOS/Signal
Identifier:          org.whispersystems.signal-desktop
Version:             7.26.0 (1)
Code Type:           ARM-64 (Native)
Role:                Default
Parent Process:      launchd [1]
Coalition:           org.whispersystems.signal-desktop [869]

Date/Time:           2024-09-27 07:34:33.9153 +0200
Launch Time:         2024-09-27 07:34:33.9031 +0200
OS Version:          macOS 15.0 (24A335)
Release Type:        User
Report Version:      104

Exception Type:  EXC_CRASH (SIGKILL (Code Signature Invalid))
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: CODESIGNING 4 Launch Constraint Violation

Triggered by Thread:  0

Thread 0 Crashed:
0   dyld_path_missing             	       0x102cf8b30 _dyld_start + 0


Thread 0 crashed with ARM Thread State (64-bit):
    x0: 0x0000000000000000   x1: 0x0000000000000000   x2: 0x0000000000000000   x3: 0x0000000000000000
    x4: 0x0000000000000000   x5: 0x0000000000000000   x6: 0x0000000000000000   x7: 0x0000000000000000
    x8: 0x0000000000000000   x9: 0x0000000000000000  x10: 0x0000000000000000  x11: 0x0000000000000000
   x12: 0x0000000000000000  x13: 0x0000000000000000  x14: 0x0000000000000000  x15: 0x0000000000000000
   x16: 0x0000000000000000  x17: 0x0000000000000000  x18: 0x0000000000000000  x19: 0x0000000000000000
   x20: 0x0000000000000000  x21: 0x0000000000000000  x22: 0x0000000000000000  x23: 0x0000000000000000
   x24: 0x0000000000000000  x25: 0x0000000000000000  x26: 0x0000000000000000  x27: 0x0000000000000000
   x28: 0x0000000000000000   fp: 0x0000000000000000   lr: 0x0000000000000000
    sp: 0x000000016d31fb40   pc: 0x0000000102cf8b30 cpsr: 0x00001000
   far: 0x0000000000000000  esr: 0x00000000  Address size fault

Binary Images:
       0x102cf4000 -        0x102d77fff dyld_path_missing (*) <02e3ca05-e849-31c8-a4f2-c7292420dfad> /dyld_path_missing
       0x102ae0000 -        0x102ae3fff main_executable_path_missing (*) <4c4c442a-5555-3144-a1a2-2351b1e9fd1c> /main_executable_path_missing
               0x0 - 0xffffffffffffffff ??? (*) <00000000-0000-0000-0000-000000000000> ???

Error Formulating Crash Report:
dyld_process_snapshot_get_shared_cache failed

EOF

Steps to reproduce

1. Start Signal
2. Signal will crash.

Expected result

I would expect signal to start and work normally.

Actual result

Signal crashes with the "Signal quit unexpectedly" message.

Screenshots

No response

Signal version

Version: 7.26.0 (1) (I think? - I cannot start Signal to see the About box)

Operating system

MacOS

Version of Signal on your phone

This is desktop version of Signal.

Link to debug log

I cannot access this as I cannot start Signal.

[scottnonnenberg-signal]

The error is curious: CODESIGNING 4 Launch Constraint Violation. What happens if you go to https://signal.org/download and install Signal Desktop again? Does that fix things? Does it then start happening when it auto-updates?

Please consider reaching out to [email protected] so you can feel confident sharing more information!

[jming422]

I had the exact same behavior as described above; I tried trashing the app, reinstalling from https://signal.org/download, and it fixed things for me!

I'll keep an eye out for the next time it auto-updates to see if it breaks again

[thomasdn]

I had the exact same behavior as described above; I tried trashing the app, reinstalling from https://signal.org/download, and it fixed things for me!

I'll keep an eye out for the next time it auto-updates to see if it breaks again

Reinstalling the app from a new download also seemed to fix the issue on my system.
However, I think there clearly seems to be a bug since multiple people end up in this situation...

[scottnonnenberg-signal]

Please let us know if the behavior comes back!