Flutterfire: [firebase_crashlytics] Support for deobfuscation of Dart reports

[kroikie]

I can't even find any info on how to find dart obfuscation maps to deobfuscate reports manually

[kroikie]

@rostopira

The issue at https://github.com/flutter/flutter/issues/30303 has been closed and moved here. Future collaboration on this issue will be done here.

[sperochon]

Hello,

I have created a web flutter app to do dart deobfuscation easily:
https://www.mobiquite.fr/dart-flutter-stacktrace-deobfuscator/

It is inspired from the script of @rostopira
https://github.com/flutter/flutter/issues/30303#issuecomment-522544995

[kikuchy]

Any update?

[rostopira]

@kikuchy yep, update: https://flutter.dev/docs/deployment/obfuscate
@kroikie Please, close this issue, it's resolved

[rostopira]

Oops, missed that issue is about crashlytics, not only obfuscation, should not be closed

[lsuhov]

Hello,
Please prioritize the deobfuscation of dart stack traces in Crashlytics. How are the production Flutter apps managing this part? I doubt that flutter symbolize can be considered a reasonable solution if you have multiple exceptions to check.

Ideally the complete solution should be offered with firebase_app_distribution from fastlane.

[2math]

Best solution is to be able to upload the symbols per version in firebase and crashlitics to be able to translate the exception.
Something like mappings on Play Store

[singun-lxd]

Any solutions?

[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?

[nt4f04uNd]

@talent-apps it's not, you still can manually deobfuscate crash reports

[dluksza]

@nt4f04uNd the first step would be to include this information in the README and document how to do this manually. I've tried deobfuscating my crash reports manually but it never worked for me.