Troubleshooting

Sentry CLI not configured

The following message may appear in your build output:

The Sentry CLI is not fully configured with authentication, organization, and project.

The message currently appears as information only, though we may change it to a warning in the future. This means that you are building in Release configuration, and you have not fully configured the Sentry CLI integration. You can handle this in one of the following ways:

• You can enable the Sentry CLI integration by providing configuration details, as described in the documentation here.

• You can prevent the message from being generated by setting the property <UseSentryCLI>false</UseSentryCLI> in your .NET project file, or with /p:UseSentryCLI=false on the command line to dotnet build or msbuild. The Sentry CLI integration will be disabled.

• You can do nothing, and just ignore the message. The Sentry CLI integration will be disabled.

Keep in mind that if the Sentry CLI integration is disabled, then debug information files such as PDB symbols will not be sent to Sentry. If Sentry cannot locate symbols, then it cannot perform symbolication of stack traces. This means that for some types of projects (depending on configuration), you may not see filenames and line numbers to help you locate the source of an exception.

The event is dropped by Sentry because it's too large

Sentry: (Error) Sentry rejected the envelope 5bfe4129cb2446c08768b16479865035. Status code: RequestEntityTooLarge. Error detail: failed to read request body. Error causes: A payload reached size limit..

You can have the Sentry .NET SDK write these envelopes to a path in order to troubleshoot why they are too large. Set the environment variable SENTRY_KEEP_LARGE_ENVELOPE_PATH to the directory you want these to be written to. Make sure the process the SDK is running in has write access to it.

User IP address in Sentry shows up as the server IP

If you're using a proxy server that relies on X-Forwarded-For, you might need to configure ASP.NET Core so that it's aware of it.

See this GitHub issue for more context.

Unhandled exceptions are not captured when using an async Main method

Starting with C# 7.1, a program's Main method can be declared either synchronously or asynchronously. However, the asynchronous approach is not fully compatible with the Sentry SDK. If your application uses an async Main method, the Sentry SDK will be disposed before an unhandled exception can be captured.

In other words, this is insufficient:

static async Task Main()
{
    using var _ = SentrySdk.Init(o => { /* your options */ });
    await DoSomethingAsync(); // an unhandled exception here will not be captured by Sentry
}

There are two different ways to work around this issue:

• You can avoid unhandled exceptions by wrapping your code in a try/catch block:

  C#

  Copied

  static async Task Main()
  {
      using var _ = SentrySdk.Init(o => { /* your options */ });
      try
      {
          await DoSomethingAsync();
      }
      catch (Exception ex)
      {
          SentrySdk.CaptureException(ex);
      }
  }

• You can use a synchronous Main method to ensure the Sentry SDK isn't disposed prematurely:

  C#

  Copied

  static void Main()
  {
      using var _ = SentrySdk.Init(o => { /* your options */ });
      MainAsync().GetAwaiter().GetResult();
  }
  
  static async Task MainAsync()
  {
      await DoSomethingAsync();
  }

  Note that with this approach, it is not advised to use .Wait() or .Result, as that would wrap unhandled exceptions in an AggregateException.

See this GitHub issue for more context.

The call is ambiguous between the following methods or properties:
Sentry.SentryOptionsExtensions.DisableDiagnosticSourceIntegration(Sentry.SentryOptions)
and Sentry.SentryOptionsDiagnosticExtensions.DisableDiagnosticSourceIntegration(Sentry.SentryOptions)

Debug: Logging enabled with ConsoleDiagnosticLogger and min level: Debug
Debug: Initializing Hub for Dsn: 'https://examplePublicKey@o0.ingest.sentry.io/0'.
Debug: Using 'GzipBufferedRequestBodyHandler' body compression strategy with level Optimal.
Debug: New scope pushed.
Debug: Registering integration: 'AutoSessionTrackingIntegration'.
Debug: Registering integration: 'AppDomainUnhandledExceptionIntegration'.
Debug: Registering integration: 'AppDomainProcessExitIntegration'.
Debug: Registering integration: 'TaskUnobservedTaskExceptionIntegration'.
Debug: Registering integration: 'SentryDiagnosticListenerIntegration'.

using SentrySession = Sentry.Session;