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
Look at any issue reported from a Flutter/Dart app. Navigate to stack trace and turn on the "Raw stack trace" option.
The presented Dart stack trace look something like this:
File "my_api.g.dart", line 975, in MyPeripheralManagerHostApi.startAdvertising
File "<asynchronous suspension>"
File "my_peripheral_manager.dart", line 138, in MyPeripheralManager.startAdvertising
File "<asynchronous suspension>"
File "sync_ble_controller.dart", line 148, in SyncBleController._initBlePeripheral
Expected Result
The raw/native stack trace format for Dart for the above trace should look something like this. Also note the package reference and the source path missing from the current Sentry's "raw stack trace" presentation, which is required in order to uniquely identify source of the issue.
The Dart stack trace presentation in the Sentry's web UI is not anywhere alike Dart's native/raw stack trace (e.g. if you catch and print stack trace in the Dart code).
Also if you copy it from the Sentry web UI, the stack trace format is not recognized by the Dart tools, e.g. "Code / Analyze Stack Trace or Thread Dump..." action in the IntelliJ Dart/Flutter plugins and as a result you can't easily navigate to the source code from the stack trace analysis view in the IDE.
Are you willing to submit a PR?
None
The text was updated successfully, but these errors were encountered:
Platform
Dart
Obfuscation
Disabled
Debug Info
Disabled
Doctor
N/A
Version
8.1.0
Steps to Reproduce
Look at any issue reported from a Flutter/Dart app. Navigate to stack trace and turn on the "Raw stack trace" option.
The presented Dart stack trace look something like this:
Expected Result
The raw/native stack trace format for Dart for the above trace should look something like this. Also note the package reference and the source path missing from the current Sentry's "raw stack trace" presentation, which is required in order to uniquely identify source of the issue.
Actual Result
The Dart stack trace presentation in the Sentry's web UI is not anywhere alike Dart's native/raw stack trace (e.g. if you catch and print stack trace in the Dart code).
Also if you copy it from the Sentry web UI, the stack trace format is not recognized by the Dart tools, e.g. "Code / Analyze Stack Trace or Thread Dump..." action in the IntelliJ Dart/Flutter plugins and as a result you can't easily navigate to the source code from the stack trace analysis view in the IDE.
Are you willing to submit a PR?
None
The text was updated successfully, but these errors were encountered: