اتصال کاربر واردشده به خطاها

When a user writes "the app crashed", you want their errors, not everyone's. Abrova Trace takes a user id and puts it on every error, native crash and log line after that. Abrova Auth already knows the id, and its authStateChanges stream tells you every time it changes. One listener connects the two.

Trace needs only the user id, never the user's token, e-mail or name.

1Start both SDKs#

Both packages come from Abrova Center (see the Trace Flutter SDK and Auth Flutter SDK for the Android and iOS repository lines):

# pubspec.yaml
dependencies:
  abrova_trace_flutter_sdk:
    hosted: https://center.abrova.ir/api/packages/abrova/pub
    version: ^0.2.6
  abrova_auth:
    hosted: https://center.abrova.ir/api/packages/abrova/pub
    version: ^0.1.1

Start Trace first, with initWithZone, and Abrova Auth inside its callback. Both use the same public key:

import 'package:flutter/material.dart';
import 'package:abrova_trace_flutter_sdk/abrova_trace_flutter_sdk.dart';
import 'package:abrova_auth/abrova_auth.dart';

const abrovaApiKey = 'ab_live_your_api_key';

void main() async {
  await AbrovaTrace.initWithZone(
    AbrovaTraceConfig(apiKey: abrovaApiKey, release: '1.0.0'),
    () async {
      WidgetsFlutterBinding.ensureInitialized();
      await AbrovaAuth.initialize(abrovaApiKey); // restores the saved session
      followSignedInUser(); // step 2
      runApp(const MyApp());
    },
  );
}

2Follow the user with one listener#

authStateChanges emits the current user first, then again on every sign-in, sign-out and profile change. Set the Trace user id each time:

import 'dart:async';

StreamSubscription<AbrovaAuthUser?>? _traceUserSub;

void followSignedInUser() {
  _traceUserSub ??= AbrovaAuth.instance.authStateChanges.listen((user) {
    if (user != null) {
      AbrovaTrace.setUserId(user.id); // ru_…
    } else {
      AbrovaTrace.setUserId(''); // signed out: later errors carry no user id
    }
  });
}

Because the stream starts with the current user, a user restored from the saved session is set at launch too, before anything can fail. Guests count: an anonymous user has an id like any other (see Sign in guests and upgrade them later), and when a guest links a sign-in method the id stays the same.

The Flutter Trace SDK has no separate call to clear the user, so an empty id stands for "nobody signed in".

3Optional: say whether it is a guest#

Whether the user is still a guest often matters when you read an error. Add it as a tag in the same listener:

if (user != null) {
  AbrovaTrace.setUserId(user.id);
  AbrovaTrace.setTag('account', user.anonymous ? 'guest' : 'member');
}

Keep it to the id and coarse facts like this. Don't send e-mail addresses, names or phone numbers to Trace unless you really need them.

4Check that it worked#

1. Sign in on a test device, then cause an error, for example with a button whose onPressed is () => throw StateError('Abrova user test').
2. In Abrova Console → Trace → Issues, open the issue. In the Context card, Extra data shows user_id with the Abrova Auth id, and the Breadcrumbs include User ID set.
3. In Abrova Auth › Users, look up that id: it is the user you signed in as.

An issue groups every repeat of the same error and keeps the extra data of the latest occurrence, so the issue shows the user it last happened to.

5Crashes and logs carry it too#

You don't need more code for these:

• Native crashes on Android and iOS: setUserId passes the id to the bundled native SDK, so the crash report sent on the next launch is tagged with the same user.
• Logs you send with AbrovaTrace.info(…) and the other level helpers after enabling logging carry the user id as well: open an entry in Trace → Logs and its details show the User ID.

Troubleshooting#