In the page 'Uploading Debug Symbols', the section 'Xcode Build Phase' lists two different script options which can be copy-pasted into a new Xcode build phase. It seems like if sentry-cli has been installed via Homebrew (which is listed in its documentation as one of the installation methods) on an Apple Silicon Mac, the scripts will log a warning/error that sentry-cli is not installed (even though it's accessible from Terminal)
Suggested Solution
SwiftLint's Xcode build phase documentation section mentions the following, which I think might be applicable to Sentry (at least, it fixed Sentry's script issue for me!), and could be mentioned in the Uploading Debug Symbols page:
If you installed SwiftLint via Homebrew on Apple Silicon, you might experience this warning:
That is because Homebrew on Apple Silicon installs the binaries into the /opt/homebrew/bin folder by default. To instruct Xcode where to find SwiftLint, you can either add /opt/homebrew/bin to the PATH environment variable in your build phase
if [[ "$(uname -m)" == arm64 ]]; then
export PATH="/opt/homebrew/bin:$PATH"
fi
// ...
or you can create a symbolic link in /usr/local/bin pointing to the actual binary:
Core or SDK?
Platform/SDK
Which part? Which one?
iOS SDK
Description
In the page 'Uploading Debug Symbols', the section 'Xcode Build Phase' lists two different script options which can be copy-pasted into a new Xcode build phase. It seems like if sentry-cli has been installed via Homebrew (which is listed in its documentation as one of the installation methods) on an Apple Silicon Mac, the scripts will log a warning/error that sentry-cli is not installed (even though it's accessible from Terminal)
Suggested Solution
SwiftLint's Xcode build phase documentation section mentions the following, which I think might be applicable to Sentry (at least, it fixed Sentry's script issue for me!), and could be mentioned in the Uploading Debug Symbols page: