Stack Traces

Stack traces show the exact sequence of function calls leading to an error — revealing WHERE it happened, HOW the code got there, and WHAT functions were called.

Automatic Stack Trace Capture#

No additional configuration needed. AbrovaTrace automatically captures stack traces from:

• Uncaught exceptions (with captureUncaughtErrors: true)
• Manual exception captures (with captureException())
• Async errors (with initWithZone())
• Platform exceptions from native code

try {
  await riskyOperation();
} catch (e, stackTrace) {
  await AbrovaTrace.captureException(
    e,
    stackTrace: stackTrace, // Always include this!
    message: 'Operation failed',
    extra: {'user_id': 'user_123'},
  );
}

Reading Stack Traces#

• Top line: Where the error occurred
• Following lines: The call stack (how the code got there)
• File paths & line numbers: Help locate the exact issue

Platform-Specific Stack Traces#

Adding Context to Stack Traces#

try {
  await processPayment(orderId, amount);
} catch (e, stackTrace) {
  await AbrovaTrace.captureException(
    e,
    stackTrace: stackTrace,
    message: 'Payment processing failed',
    extra: {
      'order_id': orderId,
      'amount': amount,
      'payment_method': paymentMethod,
    },
  );
}

Native Crash Stack Traces#

Native crashes are detected on the next app launch. When a crash kills the app, it can't report in real-time — so AbrovaTrace detects it on restart.

Uploading Source Maps#

For web platforms (Next.js, Flutter Web), upload .map files so production stack traces resolve to your original source files and line numbers.

Where to upload

• Abrova Console — at console.abrova.ir → your project → Trace → Source maps & symbols. Set the release version and upload your .map files (several in one go).
• Abrova CLI — upload from your build or CI with abrova-trace sourcemaps upload. See Upload Source Maps.
• The Abrova desktop app will offer the same upload when it launches (coming soon).

The release version must match the release field you pass to the SDK at init — that's how the backend pairs the right map with each error.

Uploading needs the member role or higher; deleting uploaded files needs admin or owner. See Roles & Permissions.

Next.js

// next.config.js
module.exports = {
  productionBrowserSourceMaps: true,
};

After next build, you'll find the .map files next to the chunks under .next/static/chunks/. Up to 500 .map files are accepted per upload, so you can drop them all at once (non-.map files are skipped).

Flutter Web

Build with source maps enabled, then upload the single main.dart.js.map:

flutter build web --source-maps

The map will be at build/web/main.dart.js.map.

flutter build web --source-maps --dart2js-optimization=O1

Best Practices#