Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Cannot inject - operation not permitted (MacOS)

Open
#13 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
go, macos

Research direction

Start by reproducing bdcli install --channel stable on macOS Tahoe and capture the failure while writing to /Applications/Discord.app/Contents/Resources. Compare the CLI behavior with the linked Installer issue; done means identifying the cause of the permission failure and confirming that installation succeeds without the reported error.

Written by the indexing model from the issue text.

Description

Using MacOS Tahoe 26.6.2 (latest).
Upon update to v1.0.0 it showed multiple "cannot verify it's free of malware" prompts, and even after allowing it through Privacy & Security it's still showing an error when injecting.

🛠 Preparing BetterDiscord...
✅ Directory exists: /Users/choccy/Library/Application Support/BetterDiscord/data
✅ Directory exists: /Users/choccy/Library/Application Support/BetterDiscord/plugins
✅ Directory exists: /Users/choccy/Library/Application Support/BetterDiscord/themes
✅ BetterDiscord prepared for install

📥 Downloading BetterDiscord...
✅ Downloaded BetterDiscord version v1.14.0 from the official website
✅ BetterDiscord downloaded

✅ Discord is not running.

🔌 Injecting into Discord...
❌ Cannot write to /Applications/Discord.app/Contents/Resources
   open /Applications/Discord.app/Contents/Resources/.bd-write-probe-351104156: operation not permitted
Error: installation failed: open /Applications/Discord.app/Contents/Resources/.bd-write-probe-351104156: operation not permitted

Here's what I got when I uninstalled and reinstalled:

==> Installing Cask bdcli
==> Linking Binary 'bdcli' to '/opt/homebrew/bin/bdcli'
Warning: An exception occurred within a child process:
  RuntimeError: Failed to generate bash completions from /opt/homebrew/Caskroom/bdcli/1.0.0/bdcli: Failure while executing; `\{\"SHELL\"\ =\>\ \"bash\"\} /opt/homebrew/Caskroom/bdcli/1.0.0/bdcli completion completion bash` was terminated by uncaught signal KILL. Here's the output:

Failed to generate zsh completions from /opt/homebrew/Caskroom/bdcli/1.0.0/bdcli: Failure while executing; `\{\"SHELL\"\ =\>\ \"zsh\"\} /opt/homebrew/Caskroom/bdcli/1.0.0/bdcli completion completion zsh` was terminated by uncaught signal KILL. Here's the output:

Failed to generate fish completions from /opt/homebrew/Caskroom/bdcli/1.0.0/bdcli: Failure while executing; `\{\"SHELL\"\ =\>\ \"fish\"\} /opt/homebrew/Caskroom/bdcli/1.0.0/bdcli completion completion fish` exited with 1. Here's the output:

Failed to generate pwsh completions from /opt/homebrew/Caskroom/bdcli/1.0.0/bdcli: Failure while executing; `\{\"SHELL\"\ =\>\ \"pwsh\"\} /opt/homebrew/Caskroom/bdcli/1.0.0/bdcli completion completion powershell` exited with 1. Here's the output:

Then got these two password prompts twice (4x total):
"git-credential-osxkeychain wants to use your confidential information stored in "github.com" in your keychain."
"git-credential-oskeychain wants to access key "github.com" in your keychain."
Allowing all of them and running bdcli install --channel stable leads to the first "operation not permitted" error.

When trying the installer app, I get the same result as this issue from the installer repo.

Dominant language
Go
Stars
22
Forks
3
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from BetterDiscord/cli

All issues in BetterDiscord/cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.