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

When capturing already captured Error ref session should be still updated #14752

Open
krystofwoldrich opened this issue Dec 17, 2024 · 0 comments
Labels
Package: browser Issues related to the Sentry Browser SDK

Comments

@krystofwoldrich
Copy link
Member

krystofwoldrich commented Dec 17, 2024

try {
  thisFunDoesNotExist();
} catch (error) {
  Sentry.captureException(error);
  throw error; // assume this is not catch anywhere else until global error handler
}

The example above shows code snippet which causes the session not being marked as crashed.

But the error reached the global handler and the session should be marked as crashed.

@github-actions github-actions bot added the Package: browser Issues related to the Sentry Browser SDK label Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Package: browser Issues related to the Sentry Browser SDK
Projects
None yet
Development

No branches or pull requests

1 participant