Flutter SDK

Call init once, as early as possible — the first line of main(), before runApp:

import 'package:logtryl_crash/logtryl_crash.dart';

Future<void> main() async {
  await LogtrylCrash.init('YOUR_PROJECT_KEY');
  runApp(const MyApp());
}

Grab your project key from the project’s Edit page in the Dashboard or Desktop app — see Getting your project key on the SDK Overview page.

The easiest way in is the built-in LogtrylPairingDrawer widget — a swipe-out drawer with a code-entry UI:

LogtrylPairingDrawer(
  edge: PairingDrawerEdge.right,
  child: const MyApp(),
);

Or drive it yourself with LogtrylCrash.pairDevice(code) / .isPaired() / .unpairDevice().

Flag a caught exception as worth including in the active recording, even though it didn’t crash the app:

try {
  await riskyOperation();
} catch (e, stack) {
  LogtrylCrash.recordHandledError(e, stack);
}

This only does anything while a debug recording is active — it’s not general-purpose logging.

• LogtrylCrash.init(appKey, { apiBaseUrl }) — installs fatal-crash capture and configures pairing/polling. appKey is your project key (see above).
• LogtrylCrash.recordHandledError(error, [stackTrace]) — manually records a caught exception into the active recording.
• LogtrylCrash.pairDevice(code) / .isPaired() / .unpairDevice() — drive pairing yourself instead of (or alongside) LogtrylPairingDrawer.
• LogtrylCrash.getPendingCrashReports() / .onCrashReport — read fatal crash reports captured on this device directly, for your own logging/QA needs on top of what Logtryl already shows.