App crashes with QuickLookUI error on macOS

[quanglam2807]

We're not sure if this is a general electron issue or specific to the Castlabs Electron version. Since we're using Castlabs Electron, we're reporting it here first.

We've received multiple reports from users experiencing crashes on macOS 11 after upgrading from Electron 33.x+wvcus to 34.x+wvcus. Below is the crash log:

Crashed Thread: 0  

Exception Type: EXC_CRASH (SIGABRT)  
Exception Codes: 0x0000000000000000, 0×0000008000080000  
Exception Note: EXC_CORPSE_NOTIFY  

Termination Reason: DYLD, [0x1] Library missing  

Application Specific Information:  
dyld: launch, loading dependent libraries  

Dyld Error Message:  
dyld: Using shared cache: 90D5D492-04EA-3BDA-9213-A2AD40F101F5  
Library not loaded: /System/Library/Frameworks/QuickLookUI.framework/Versions/A/QuickLookUI  

It seems this could be related to Electron being built with Xcode 16, as discussed in these reports:

• Fails to launch under macOS 10.14.6 when built with Xcode 16 Sequel-Ace/Sequel-Ace#2105
• https://forums.developer.apple.com/forums/thread/763710

There may be a need to adjust the Xcode build configuration, as suggested in this PR:

• https://github.com/Sequel-Ace/Sequel-Ace/pull/2108/files

Could you take a look? If this is an upstream issue, we’ll report it there instead.

Thanks!

[quanglam2807]

CC: @khwaaj! tysm!

[quanglam2807]

After looking into Info.plist file, I've confirmed that the mainline electron is built with Xcode 15.4 while castlabs-electron is built with Xcode 16.2 => this bug only occurs with castlabs-electron because of a bug in Xcode 16: https://forums.developer.apple.com/forums/thread/763710

[khwaaj]

Yes, I came to the same conclusion after looking briefly into this last week. I meant to write something in the thread but I didn't get around to it before I had a mini vacation over the weekend.

Anyway, this is clearly an Xcode issue at the core. Unfortunately we can't easily work around it with the current build setup for ECS either, so I'm not entirely sure when it can be fixed. Since the issue is acknowledged as a known issue, maybe Apple will even fix Xcode before that happens.