When capturing already captured Error ref session should be still updated

[krystofwoldrich]

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.

[lforst]

So we established a while ago that manual captureException calls count as handled and will therefore not mark sessions as crashed.

Besides this case being incredibly hard/impossible to solve, we would have to store the originally captured error indefinitely until we would know that it bubbled up to a global error, "logging and rethrowing" is somewhat of an antipattern in general everywhere.

Unless I completely missed the point here, I'll close this issue.