macos: mcumgr process killed

[homburg]

I am trying to connect with mcumgr, but the process seems to be killed, .eg

❯ ./mcumgr --loglevel debug --conntype ble --connstring peer_name=something echo conn_test
DEBU[2020-12-11 13:06:59.936] Using connection profile: name=unnamed type=ble connstring=peer_name=something
[1]    59676 killed     ./mcumgr --loglevel debug --conntype ble --connstring peer_name=something ech

Password:
DEBU[2020-12-11 13:11:35.413] Using connection profile: name=unnamed type=ble connstring=peer_name=something
[1]    60061 killed     sudo ./mcumgr --loglevel debug --conntype ble --connstring peer_name=somethin

Can you help with any explanation why the process might be killed?

Versions

go

go version go1.14.4 darwin/amd64

macOS

macOS Big Sur 11.0.1

Shell

zsh 5.8 (x86_64-apple-darwin19.3.0)

[homburg]

Might be this go issue: golang/go#19734 (comment)

Testing

Tried strategies from golang#19734 without success:

• Updating/reinstalling go (to version 1.15.6)
• Building with go build -ldflags -s

[paulrouget]

Running into the same issue. Any idea what's going on?

[kabbi]

Got the same issue. It's not related to golang bug of 2017, it's related (at least in my case) to bluetooth privacy changes in Big Sur. This is the instructions I've found in some other bluetooth-related project that helped me (part 2, enable bluetooth access for my terminal app)

To use Bluetooth on macOS Big Sur (11) or later, you need to either package your binary into an application bundle with an Info.plist including NSBluetoothAlwaysUsageDescription, or (for a command-line application such as the examples included with btleplug) enable the Bluetooth permission for your terminal. You can do the latter by going to System Preferences → Security & Privacy → Privacy → Bluetooth, clicking the '+' button, and selecting 'Terminal' (or iTerm or whichever terminal application you use).