You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This creates challenges for accurately monitoring and diagnosing issues in production environments where Flutter code is obfuscated. Otherwise, to see many of the benefits of using New Relic, we have to turn off flutter obfuscation.
Obfuscation is an important security measure to protect code from being viewed and reverse engineering. Without support for obfuscation, the New Relic reporting is unable to provide accurate data about crashes, exceptions, and log events.
Expected Behavior:
It would be beneficial to have a similar tool like run-symbol-tool that is in the iOS agent, but for Flutter apps.
Hi, Chris. Thanks for reaching out. We are on the same page. Unpacking obfuscated crashes is high on our list of priorities. We will be adding this often requested feature to all of our mobile platforms (React Native, Flutter, Xamarin, Maui, Cordova etc..) throughout the remainder of the year. Again, thank you for submitting this feedback. John
Issue Description:
From what I can see New Relic does not support .symbols file uploads that are created when a flutter app is obfuscated.
https://docs.flutter.dev/deployment/obfuscate
This creates challenges for accurately monitoring and diagnosing issues in production environments where Flutter code is obfuscated. Otherwise, to see many of the benefits of using New Relic, we have to turn off flutter obfuscation.
Obfuscation is an important security measure to protect code from being viewed and reverse engineering. Without support for obfuscation, the New Relic reporting is unable to provide accurate data about crashes, exceptions, and log events.
Expected Behavior:
It would be beneficial to have a similar tool like
run-symbol-tool
that is in the iOS agent, but for Flutter apps.flutter build ipa --obfuscate --split-debug-info=/<project-name>/<directory>
upload-symbols --symbols-file=/<project-name>/<directory>
The text was updated successfully, but these errors were encountered: