Skip to content

captureException with POJO shows Sentry internal as top stack frame #8296

@Dodie324

Description

@Dodie324

Is there an existing issue for this?

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/react

SDK Version

7.54.0

Framework Version

React 18

Link to Sentry event

https://afresh.sentry.io/issues/4232470254/?project=5540748&referrer=slack

SDK Setup

  Sentry.init({
    dsn: vars.sentryDsn,
    environment: vars.environment,
    release: `${vars.buildNum} (${vars.buildHash})`,
  })

  Sentry.configureScope((scope) => {
    scope.setExtra('actor', 'web-client')
    scope.setTag('client_version', vars.appVersion)
  })

Steps to Reproduce

After upgrading @sentry/react from v6.11 -> v7.54, the source map where the exception gets triggered is different from what it typically is, and as a result, generates a weird issue title when logged to our dashboard. Am I missing something in the update?

v.6.11

Screenshot 2023-06-06 at 20 02 05 Screenshot 2023-06-06 at 20 02 18

v.7.54

Screenshot 2023-06-06 at 20 02 31 Screenshot 2023-06-06 at 20 02 44

Expected Result

I'd expect logging to remain the same

Actual Result

Source maps appear to be wrong, and is generates a weird title in the Issues dashboard

Metadata

Metadata

Assignees

Labels

No labels
No labels
No fields configured for issues without a type.

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions