Skip to content

Connect Dart with its Sentry SDK

Your Dart app keeps its Sentry SDK. Xovris gives it your project’s DSN, and every error it sends becomes a Xovris issue with its stack and release.

Terminal window
dart pub add sentry
Get your project’s DSN

Already installed? Your code stays as it is – the DSN is the one change.

Start it

Put this at the top of main():

import 'dart:io';import 'package:sentry/sentry.dart';
Future<void> main() async {  await Sentry.init((options) => options.dsn = Platform.environment['SENTRY_DSN']);}

It reads SENTRY_DSN, so your project’s address never sits in your code.

Your project’s DSN

Xovris finds the SDK in your pubspec.yaml, creates your project’s address and writes it as SENTRY_DSN in your env file, after showing you the change. It then sends a test event and waits until it is stored. In the project, run:

Terminal window
npx xovris@latest init

See the first error

Send one from anywhere your app runs:

await Sentry.captureException(Exception('first error for Xovris'));

Capture one error with the SDK’s own call and it appears as a Xovris issue:

  • Errors and their stack traces, grouped into issues
  • Messages you capture
  • The release each event names

Its frameworks

The same DSN covers every framework this SDK’s own integrations reach:

Flutter.

What Xovris has run

Driven with the real SDK: sentry 10.4.0 from pub.dev (the core sentry_flutter runs on) on the Dart SDK 3.14, captured 2026-11-14 (a chunked gzip envelope). Its own bytes are replayed into Xovris on every change.

Every option the SDK has is in its own documentation: docs.sentry.io/platforms/dart/

Ask Xovris

Open the full page

Your data is never used to train our AI. How your data is kept

A problem is called fixed only once it works again. How each fix is checked

XOVRIS LTD, registered in England and Wales, company number 17499910. Registered office: 66 Paul Street, London EC2A 4NA.