Getting SIGKILL error

[tlherysr]

Describe the bug
I cannot run supabase command on my Mac. Getting SIGKILL signal.

To Reproduce
Steps to reproduce the behavior:

1. Install supabase with this command: brew install supabase
2. Run supabase --help after installation.
3. See error

Expected behavior
Supabase cli should print the help text.

Screenshots

System information
Rerun the failing command with --create-ticket flag.

• Ticket ID: I cannot even run the cli tool so cannot run it with --create-ticket flag.
• Version of OS: MacOS 27 Developer Beta
• Version of CLI: 2.105.0
• Version of Docker: Docker version 29.5.3
• Versions of services: I cannot run supabase command.

[veilofsecurity]

Same issue. Tried latest beta and no change.

[avallete]

Hi! Thanks for the report. Since you're on the macOS 27 Developer Beta (and this doesn't reproduce on stable macOS 26.x), we suspect the new OS is killing the binary at launch most likely due to stricter code-signature enforcement or the Rosetta 2 removal in Golden Gate. Could you run the following commands and paste the output so we can confirm which one it is?

1. Check the binary architecture vs your machine:

file $(which supabase)
uname -m

2. Check how the binary is signed:

codesign -dvv $(which supabase)

3. Get the exact kill reason from the system log (run supabase --help first, then immediately):

log show --last 2m --predicate 'sender == "AppleMobileFileIntegrity" OR process == "supabase"' --info

If macOS generated a crash report, it would also help to attach the most recent supabase-*.ips file from ~/Library/Logs/DiagnosticReports/.

In the meantime, two workarounds you can try:

• If step 1 shows x86_64 (Intel binary on Apple Silicon): macOS 27 uninstalls Rosetta 2 on upgrade. Either reinstall it with softwareupdate --install-rosetta, or better, reinstall the CLI through an ARM-native Homebrew (/opt/homebrew). Make sure you're on Homebrew 6.0.0+ (brew --version), which is the first version with macOS 27 support.

• If step 2 shows linker-signed / no TeamIdentifier: try re-signing the binary in place:

  codesign --force -s - $(which supabase)

Let us know what you find thanks!

[tlherysr]

re-signing the binary solved the problem. Thanks.

For the solution, I just ran this command:
codesign --force -s - $(which supabase)