-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
obfuscation: flutter/dart code obfuscation support with crash log readability as normal #191
Comments
Hi Jignesh! I understand what you mean, Raygun has support for Sourcemaps for Flutter web but not for Flutter obfuscation symbol files. I'm checking with the team, and we will get back to you. |
Thank you so much @miquelbeltran for this confirmation 👍 |
@JigneshWorld and others. Just wanted to let folks know that the Raygun team is looking into this. A temporary (totally acknowledging that this far from ideal) solution for you is:
You'll need to replace the symbols file with the one that matches the app version of your release and uses the correct architecture. On Android that will in most cases be arm64 though, but you can't fully rely on that heuristic. |
The Readme has been updated with instructions to deobfuscate stack-traces from Raygun. Note that the architecture is listed in the stack-trace itself. |
Thank you so much for these notes @TheRealAgentK @miquelbeltran 👍 |
Please describe your new feature request
I would like to explore this code obfuscation support with Raygun Crash Reporting.
https://docs.flutter.dev/deployment/obfuscate
I found this document for Android but not much on the dart/flutter side.
https://raygun.com/documentation/language-guides/android/crash-reporting/proguard/
https://raygun.com/documentation/language-guides/flutter/crash-reporting/installation/
Would you please help to understand does it is currently supported or requires some work on the platform/SDK side to support this?
If it's supported currently - would you please help to navigate towards the helpful resources?
The text was updated successfully, but these errors were encountered: