Sentry CLI Options
Learn more about how to configure the options used by Sentry CLI.
The Unity SDK includes Sentry CLI as a tool to upload debug symbols to Sentry. These debug symbols are used in processing events sent to Sentry to provide stacktraces and linenumbers. This page describes the options available to configure the Sentry CLI.
Similar to the programmatic configuration of the SDK itself, the debug symbol upload via Sentry CLI also supports programmatic configuration.
The Configure callback gets invoked during the build process and allows you to modify the options used by Sentry CLI.
UploadSymbols
Whether the SDK should automatically upload debug symbols to Sentry. This requires a valid auth token, organization, and project.
UploadDevelopmentSymbols
Whether the SDK should automatically upload debug symbols to Sentry for development builds.
UploadSources
Whether the SDK should automatically upload sources to Sentry; this enables Sentry to provide source-context on events.
UrlOverride
This option allows you to override the default Sentry URL in case you are using a self-hosted Sentry instance or a custom domain.
Auth
The auth token to use when uploading symbols to Sentry.
Organization
The organization to use when uploading symbols to Sentry.
Project
The project to use when uploading symbols to Sentry.
IgnoreCliErrors
If set to true, the Sentry CLI will not exit with an error code if it encounters an error. BE AWARE you might have unminified/unsymbolicated crashes in production if the debug symbol upload fails. When using this flag, you should store built sourcemaps and debug files, to re-run the upload symbols command at a later point.
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").