macOS Codesigning error mid way through sentry-cli run

[john-paulsmith]

Environment

sentry-cli 2.20.5. macOS 13.5 on Apple silicon.

Steps to Reproduce

Run at the root of a large built software project: sentry-cli upload-dif --include-sources -o _redacted_ -p _redacted_ --wait .

Expected/Actual Result

Using the x86_64 build of sentry-cli, this upload succeeds, but with the arm64 build, it is killed by the kernel. Unlike typical codesigning errors which occur immediately when the program starts, this process is killed part way through its run. As you can see from the attached crash dump, there are many threads running, and the crash is in thread 1 where goblin is parsing a binary.

I have tried the usual steps to resolve codesigning errors, including:

• Ensuring there are no extended attributes on the file
• Copying it to a different location
• Re-signing it locally with an ad-hoc signature then copying it.
• Right-clicking in Finder and choosing Open...
• Downloading it via a web browser and using the installation script via curl | bash.

Running sentry-cli --version succeeds.

Logs

sentry-cli-output-2.20.5.txt sentry-cli-2023-08-11-122801.txt sentry-cli-2023-08-11-122801.txt should be renamed to .ips and opened with Console.app on macOS.

[loewenheim]

Hi, where did you get the sentry-cli binary from?

[john-paulsmith]

I tried various methods:

• Downloaded directly from the GitHub releases page using a browser
• Downloaded from the GitHub releases page using curl
• curl -sL https://sentry.io/get-cli/ | INSTALL_DIR=. SENTRY_CLI_VERSION=2.20.5 bash as recommended in the README

All gave the same results. Also, when I first encountered this, 2.20.4 was the current version and that exhibited the same problem.

[loewenheim]

Hm. So I guess it's probably not a download problem, nor something flaky that happened during release.

[john-paulsmith]

Right. My first thought was that it might be a resource exhaustion issue (max open files or similar), and in fact I did see a diagnostic message that sentry-cli had exceeded the memory dirtied per day threshold, but that the kernel took no action in response. Diag report attached. sentry-cli_2023-08-15-032810_m1mini.diag.txt

[github-actions[bot]]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀