SIGTRAP on launch

[Kreeblah]

Prerequisites

• Tried the most recent nightly build
• Checked if your issue is already reported.
• Answered all the questions in this template (Or provide a working crystal ball).

What happened?

I built from 5879679 using npm install and gulp app:package-macos (with both npm and gulp sourced from Homebrew) and when I try to run the application bundle, it closes immediately without drawing a window. Running the sieve binary inside of it in the terminal just gets me this:

fish: Job 1, './sieve' terminated by signal SIGTRAP (Trace or breakpoint trap)

What did you expect to happen?

I'd expect the application to run.

Logs and Traces

crashlog.txt

I did some investigating, and this seems to start with commit 9a03f67 Prior commits run (but do nothing after server authentication succeeds and just get stuck showing "Connecting" forever), but that's the one that starts crashing on launch.

Screenshots

N/A

Which Version

Include information about your system, server and most important if it is about the app or webextension.

• Standalone app
• macOS 15.1 on an M1 Max Macbook Pro
• Sieve/Mail Server: N/A

[Aerion]

Same behavior, but upgrading electron to v33 made it work.

• (opt) Run npm run start, the UI doesn't start - crash
• Do the replacement from 28 to 33 in package.json
• Run npm install
• (opt) Run npm run start and you'll see the UI displayed
• Run the gulp app:package-macos as before to generate the working binary

diff --git a/package.json b/package.json
index 0319fbf4..00637d07 100644
--- a/package.json
+++ b/package.json
@@ -10,7 +10,7 @@
   "devDependencies": {
     "bootstrap": "^5.2.3",
     "codemirror": "^5.65.4",
-    "electron": "^28.0.0",
+    "electron": "^33.0.0",
     "electron-packager": "^17.1.1",
     "eslint": "^8.29.0",
     "eslint-plugin-jsdoc": "^39.3.20",

[thsmi]

Sorry but closing this ticket, there is no official macOS support and never was. And it will stay this way, unless the unlikely happens and a macOS user steps up to provide tested release builds and support. Until then macOS users are basically on their your own.

You find details why there is no macOS release in the FAQ. But in short developing for macOS is extra painful, it needs dramatically more time than other developing for other OS and you need special hardware because of Apples vendor lock-in. According to the statistics, the vast majority of the users of this project use Linux, followed by Windows. The macOS fraction was always very tiny. So it is not worth investing time on macOS especially as there are more important issues like for example keeping the Thunderbird add-on alive.