Bun 1.3.12 on macOS: bun build --compile output is immediately killed on launch, same project works on 1.3.11

[isme-sun]

Hi, I’m seeing what looks like a regression in Bun 1.3.12 on macOS when using bun build --compile.

Environment

• Bun 1.3.12
• macOS on Apple Silicon (arm64)
• Installed via Bun installer, not Homebrew
• Output binary is a local compiled server executable

What I’m doing

bun build ./cli.ts --compile --outfile ./dist/logia
./dist/logia server

Observed behavior

• The compiled binary is killed immediately on startup
• Exit code is 137
• No application-level error is printed first
• The same code and build command work after downgrading Bun from 1.3.12 to 1.3.11

Expected behavior

• The compiled binary should start normally

Important detail

• This does not appear to be a runtime bug in my app logic
• No relevant project code changed between the failing and working cases
• Only the Bun version changed:
  • 1.3.12 => compiled binary gets killed on launch
  • 1.3.11 => compiled binary starts normally

System log clue

I found this in macOS system logs when launching the binary built by Bun 1.3.12:

kernel: (AppleSystemPolicy) ASP: Unable to apply provenance sandbox: ..., /path/to/dist/logia

Other notes

• file ./dist/logia reports a normal Mach-O 64-bit executable arm64
• otool -L ./dist/logia only shows normal system libs
• The binary is not signed
• spctl --assess --type execute -vv ./dist/logia reports:

invalid or unsupported format for signature

This binary is later used as a packaged sidecar, so this breaks release builds even though development mode still works.

Minimal reproduction pattern

1. On macOS arm64, install Bun 1.3.12

2. Compile a Bun server with:

   bun build entry.ts --compile --outfile ./dist/app

3. Run:

   ./dist/app

4. Process is killed immediately

5. Downgrade to Bun 1.3.11 and rebuild

6. The same binary behavior becomes normal

Question

• Is this a known regression in bun build --compile on macOS?
• Is it related to macOS provenance / AppleSystemPolicy handling in the generated binary?
• Is there a recommended workaround besides pinning Bun to 1.3.11?

If needed, I can provide a smaller repro project.

[emgeee]

+1 also seeing this issue

[village-way]

+1 for the same problem

[sandin]

+1 same here

[eznix86]

Getting the issue in the CI too

[isme-sun]

It works again on 1.3.13.😊 Loving Bun!

[mrtcmn]

Same!. That causing me considering to move with Bun, Why isn't so stable!