Skip to content
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

Closed
JigneshWorld opened this issue Aug 12, 2024 · 10 comments

Comments

@JigneshWorld
Copy link

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?

@miquelbeltran
Copy link
Collaborator

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.

@JigneshWorld
Copy link
Author

Thank you so much @miquelbeltran for this confirmation 👍

@TheRealAgentK
Copy link
Contributor

@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 create an obfuscated release build of your app and get obfuscated stack traces into RG.
  • To manually symbolize the stack trace, copy the obfuscated stack track from RG into a stack.txt and then run flutter symbolize -i stack.txt -d app.android-arm64.symbols

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.

@miquelbeltran
Copy link
Collaborator

miquelbeltran commented Aug 19, 2024

The Readme has been updated with instructions to deobfuscate stack-traces from Raygun.

Note that the architecture is listed in the stack-trace itself.

@JigneshWorld
Copy link
Author

Thank you so much for these notes @TheRealAgentK @miquelbeltran 👍

@sumitramanga
Copy link
Collaborator

Hi @JigneshWorld !

I have some great news to share. We have added in the Flutter Symbols center for your plan. Could you please test this out and let me know how this goes?

You can find the instructions here - https://github.com/MindscapeHQ/raygun4flutter?tab=readme-ov-file#using-flutter-mobilenative-symbols-within-raygun

I understand that you work with @TheRealAgentK so if there is any help needed, you may also reach out to him. Of course, you can reach out to me too

We have one slight issue with the re-process button which I'm looking to add in a fix for

Thank you,
Sumitra

@sumitramanga
Copy link
Collaborator

Hi @JigneshWorld

Happy new year!

Just checking in to see if you managed to get around to my response on our latest developments here.

Looking forward to hearing from you!

Kind regards,
Sumitra

@sumitramanga
Copy link
Collaborator

Just an update on this thread for anyone else keep an eye out. We have officially released this to the world now!

We would love any feedback you have one the experience. Feel free to ping us here or throughout customer support page - https://raygun.com/about/contact

@JigneshWorld
Copy link
Author

Hello @sumitramanga,

Happy New Year!

Thank you so much for the update on the platform and the team's efforts to add this support.

Apologies for the delayed response — I had planned to test the update soon and share my thoughts afterward, but unfortunately, I haven't had the chance to try it yet.

I'll revisit this thread once I've had an opportunity to test it.

Thanks again!

@sumitramanga
Copy link
Collaborator

sumitramanga commented Jan 9, 2025

Hi Jignesh,

Sounds good! Thank you for the update.

I'll close this thread for now but happy for this to be re opened if you want

Cheers,
Sumitra

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants