Open PDF Studio quit unexpectedly.

[raxper01gmail]

Every time that I try to open the Open PDF Studio on Mac, the error:
"Open PDF Studio quit unexpectedly.

Click Reopen to open the application again. Click Report to see more detailed information and send a report to Apple."

appears. I tried restart the mac, re-install the program and the error persist

[DutchSailor]

Thanks for the issue. We are looking for a contributor who has a mac for testing purposes. I don't have it.

[DutchSailor]

Thanks for the detailed report and the screenshots — the "About This Mac" shot is very helpful.

The most likely cause is that our macOS build is currently not code-signed and not notarized. On Apple Silicon, macOS will kill an un-notarized downloaded app at launch, which shows up exactly like the "quit unexpectedly" dialog you're seeing (rather than the usual "damaged / unidentified developer" message). We're tracking a proper fix (Developer ID signing + notarization in our release pipeline).

Quick workaround to try right now — this removes the quarantine flag that triggers the block. Open Terminal and run (adjust the path if you installed it elsewhere):

xattr -dr com.apple.quarantine "/Applications/Open PDF Studio.app"

Then launch the app again. If it starts after this, it confirms the signing/notarization cause.

To help us pin it down exactly, could you send us the actual crash log? The screenshot only shows the generic dialog — the real log has the details we need:

1. In the crash dialog, click Report… (or open Console.app → Crash Reports, or System Settings → Privacy & Security → Analytics & Improvements → Analytics Data and find the Open PDF Studio-… entry).
2. Copy the top section of the report and paste it here, specifically:
   • Crashed Thread
   • Exception Type and Exception Codes (and Termination Reason if present — e.g. anything mentioning CODESIGNING or Code Signature Invalid)
   • the first ~10 backtrace frames of the crashed thread (library/framework names matter)

Also please confirm:

• Which app version did you install (e.g. 1.71.0)?
• You're on macOS 26.5.1 / Apple Silicon (M1 Pro) — is that correct? (from your screenshot it looks like it)
• Did you download the .dmg from our GitHub Releases page?

With the crash log we can confirm whether it's the signing issue or something else. Thanks for your patience.

[WellDocumentedProject]

@DutchSailor
Just popped in here, the app isn't being blocked by macOS security now but it still fails to launch.
Console logs:
https://pastebin.com/dm0a0he6

[C1em1eb]

Same issue on a new install, M4
https://pastebin.com/BVzfG7mP

[Resrcher]

S
ame issue on a MacBook Air M5.
As Dutch Sailor mentioned, it's not being blocked by macOS security.
The app just quits while it's trying to open.

OpenPDFStudio-Launch-Attempt-Console-Log.pdf

[DutchSailor]

Bevestigd als een macOS-startcrash op Apple Silicon + macOS 26 (Tahoe) met de universal .dmg. #252 en #276 zijn hetzelfde probleem. De melding is de macOS-crashreporter ("quit unexpectedly" + "Report to Apple"), dus de app start en crasht/wordt gekild — het is géén simpele Gatekeeper-weigering.

Meest waarschijnlijke oorzaak: de universal build wordt in de release-pipeline niet gesigneerd/genotariseerd, waardoor de met lipo samengestelde binary op Apple Silicon een ongeldige handtekening kan hebben (start-kill). Een mogelijke tweede factor is de WebView-init op deze gloednieuwe OS.

Eerste mitigatie (op main, commit c65aeb8): expliciete ad-hoc signing + macOS-entitlements in de bundelconfig, zodat de universal .app na lipo correct wordt (her)gesigneerd. Alleen de macOS-bundler leest dit; Windows/Linux blijven ongewijzigd.

Wat we nog nodig hebben:

1. Kun je via de "Report…"-knop de crashlog sturen? Vooral de Exception Type en de bovenste regels van de stacktrace (faulting library). Dat bevestigt de exacte oorzaak.
2. De volledige oplossing vereist een Apple Developer ID-certificaat + hardened runtime + notarisatie in de build-pipeline (daar wordt aan gewerkt), plus een test-rebuild op een macOS 26-machine.

Deze issue blijft open tot een genotariseerde build op macOS 26 is getest.

[DutchSailor]

Resolved by #293 and the macOS CI hardening on main.

The current universal macOS build now:

• builds both Apple Silicon and Intel slices;
• passes strict code-signature verification;
• opens a visible window on macOS 26;
• reaches frontend-ready state; and
• survives the startup smoke test without a crash.

Verified in CI: https://github.com/OpenAEC-Foundation/open-pdf-studio/actions/runs/29543705706

The latest nightly publication separately encountered an external Apple notarization service HTTP 500. That affects publishing the newest DMG, not the application startup fix verified above.