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

Flutter web symbolication uses scope instead of name but the name in some cases if not all is better #791

Closed
marandaneto opened this issue May 26, 2023 · 1 comment · Fixed by getsentry/symbolicator#1246

Comments

@marandaneto
Copy link

Environment

Flutter web 3.7.x

Steps to Reproduce

Throw exception in async method.

onPressed: () async {
  await Future(() {});
  throw Exception('Test exception');
},

More context here getsentry/sentry-dart#1430 (comment)

Probably relates to dart-lang/sdk#52483 as well

Expected Result

Frame at <fn> (main.dart.js:56371:16) gets symbolicated to:

at MainApp.build.<anonymous function>(../../../lib/main.dart 25:15)

Actual Result

Frame at <fn> (main.dart.js:56371:16) gets symbolicated to:

at $async$$0(../../../lib/main.dart:25:15)

@marandaneto
Copy link
Author

@loewenheim can we do something about this during our symbolication? special case Dart/Flutter events and read the scope instead of the name when available?

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