Flutterfire: [firebase_crashlytics] No stack traces for issues on Crashlytics dashboard

[talent-apps]

After upgrading to Flutter SDK 1.17, where dart obfuscation is supported by default, no stack traces appear for crashes that originate from dart code on the Crashlytics dashboard on the Firebase console.
On earlier versions of the Flutter SDK they were reported with their obfuscated names.

[TahaTesser]

Hi @talent-apps
Can you please provide your flutter doctor -v, your flutter run --verbose and a minimal complete reproducible code sample.
Thank you

[talent-apps]

Output of flutter doctor -v:

[√] Flutter (Channel stable, v1.17.1, on Microsoft Windows [Version
10.0.18363.836], locale en-US)
• Flutter version 1.17.1 at C:\flutter
• Framework revision f7a6a7906b (2 weeks ago), 2020-05-12 18:39:00 -0700
• Engine revision 6bc433c6b6
• Dart version 2.8.2

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
• Android SDK at C:\Users\XXX\AppData\Local\Android\Sdk
• Platform android-29, build-tools 29.0.2
• ANDROID_HOME = C:\Users\XXX\AppData\Local\Android\Sdk
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
• All Android licenses accepted.

[√] Android Studio (version 3.6)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin version 45.1.1
• Dart plugin version 192.8052
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)

[√] VS Code (version 1.45.1)
• VS Code at C:\Users\XXX\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.10.2

[!] Connected device
! No devices available

! Doctor found issues in 1 category.

[talent-apps]

The relevant piece of code is the main function of the app:

void main() async {

  Crashlytics.instance.enableInDevMode = false;
  // Pass all uncaught errors to Crashlytics.
  FlutterError.onError = (FlutterErrorDetails details) {
    Crashlytics.instance.recordFlutterError(details);
  };

  runApp(App());
}

[talent-apps]

Any update on this?
The official crashlytics plugin is practically useless with Flutter 1.17.X versions.
Uncaught exceptions are not reported properly.

[renzo800000]

Please prioritize this issue, since crashlytics is useless without stack traces.

For example, If I now receive a NoSuchMethodError (toString() called on null), I have no idea where it comes from, so I can't actually fix it (and fixing issues is like the whole point of crashlytics).

[talent-apps]

Any update on this?
The fact that this ticket is still open for months is nothing short of amazing.
Crashes that occur in Flutter apps in production do not include stack traces, leaving developers practically blind and incapable of improving the stability of their Flutter apps.

[talent-apps]

Any update?
At the moment, the firebase_crashlytics plugin is useless for apps that use Dart obfuscation.
Does this plugin have any owners? Why such a crucial issue is left unaddressed?