Crashlytics - Flutter/Android Obfuscated Trace

[adriancsbna]

Hello.

I have an App made in Flutter for Android published. It uses Crashlytics so we can detect errors.
The problem is that we obfuscate the code, both in dart as indicated in this link https://flutter.dev/docs/deployment/obfuscate as well as by R8 (by default in flutter, configured with a Proguard file).

The problem is that being obfuscated, when I get the reports to Crashlytics, they arrive with the StackTrace obfuscated and I can not know how to see it without obfuscating. Attached is an image of how it appears.

I have asked for Firebase support and they have told me the following:

Upon checking your screenshot, the way how the stack traces appear non-readable is indeed strange. Currently, as much as we would like to debug this from our side, Flutter is considered one of the external frameworks that's not yet covered by Firebase support. Even though Flutter basically still belongs to Google and we recommend this library for developers looking to bind Firebase to their suitable frameworks, it is not yet considered an official Firebase SDK. Issues that occur while integrating it are being handled by the Flutter team as they have the resources to further check why crashes coming from your app appear that way.

With this, you may try to bring up this issue in the official GitHub tracker for FlutterFire here (handled by Flutter team) so that this issue can be deeply examined. And if you wish to try our official Android SDK during part of the testing, you may also try to run our quickstart app for Crashlytics which has the latest Firebase Crashlytics SDK version and see if it reproduces the same issue (if it's reproducible using the official Android SDK, we can try to troubleshoot it here as well).

Would anyone know how to read the obfuscated trace?