Crashlytics: all recordException in Firebase console are categorized and grouped under the same issue.

[lubbo]

I use recordException to log JS errors.
In Firebase console all logs are categorized and grouped under the same issue, original stack trace is hidden.

• FirebaseCrashlyticsPlugin.recordException for iOS
• PluginHandle.invoke for Android
  The need to look into issues details, one by one, to check the real problem makes the functionality pretty useless.

Is there any way to pass the stacktrace to the recordException method in order to properly group by issue in Firebase console?

[robingenz]

@NLueg Can you help out? Do you have an idea? (He implemented this feature in #201).

[NLueg]

Hey, this sounds like the feature that I proposed in #201 isn't used here. The mentioned issue is exactly the reason why I added the feature to include a JS stack trace. @lubbo you can use stracktrace-js to include the Stacktrace of an exception. By using this, every issue has its own group in the console. I use this error handler in my angular application:

import { ErrorHandler, Injectable } from '@angular/core';
import { FirebaseCrashlytics } from "@capacitor-firebase/crashlytics";
import * as StackTrace from 'stacktrace-js';

@Injectable({ providedIn: 'root' })
export class ShowAlertOnError implements ErrorHandler {
  async handleError(error: Error): Promise<void> {
    StackTrace.fromError(error).then((stackTrace) => {
      FirebaseCrashlytics.recordException({
        message: error.message,
        stacktrace: stackTrace,
      });
    });
  }
}

You need to have in mind, that you still see the minified stack trace as. the source maps shouldn't be included in the production build. But still this helps a lot in analysing upcoming issues.