-
-
Notifications
You must be signed in to change notification settings - Fork 255
captureException may fail on Web and release mode, on Chrome, if you do stackTrace.toString works but not on Safari #431
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
Comments
Chrome and Safari both record exceptions with |
Firefox also works |
@ueman just to be sure, run https://github.com/getsentry/sentry-dart/tree/main/dart/example_web which isn't the same example as tested before, on release mode. |
another thing to test is, if its actually using the given |
I tested the following scenarios: 1Flutter example at https://getsentry.github.io/sentry-dart/ on Chrome, Safari and Firefox (all on macOS) 2from Dart's web example, on Chrome, Safari, Firefox (all on macOS) try {
await buildCard();
} catch (error, stackTrace) {
final sentryId = await Sentry.captureException(
error,
stackTrace: stackTrace,
);
} 3Modified 2 to the following try {
await buildCard();
} catch (error, stackTrace) {
final sentryId = await Sentry.captureException(
error,
stackTrace: null,
);
} 3Modified 2 to the following try {
await buildCard();
} catch (error, stackTrace) {
final sentryId = await Sentry.captureException(
error,
stackTrace: StackTrace.current,
);
} 4Modified 2 to the following try {
await buildCard();
} catch (error, stackTrace) {
final sentryId = await Sentry.captureException(
error,
stackTrace: stackTrace.toString(),
);
} All scenarios work as expected. Test setup:
|
Let's just close it then @ueman , users will come to it if they see something like that, could be either an oversight during the test at that time or even an older dart/flutter issue on 1.x which isn't there anymore, thanks for testing |
#187 (comment)
Edit: This was previously tracked as a card on the kanban board and just converted to an issue.
The text was updated successfully, but these errors were encountered: