sentry-javascript: The debug_meta property is not present in the events payloads sent to Sentry

Is there an existing issue for this?

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/browser

SDK Version

7.57.0

Framework Version

No response

Link to Sentry event

https://sunpower-firmware-eng.sentry.io/issues/4305936715/events/5018cadb3310433bb1b3e4d789438d5c/

SDK Setup

Sentry.init({
    dsn: process.env.REACT_APP_SENTRY_DSN,
    maxBreadcrumbs: 20,
    release:  process.env.REACT_APP_RELEASE,
    replaysSessionSampleRate: 0.1,
    replaysOnErrorSampleRate: 1.0,
    environment: process.env.REACT_APP_ENV,
    transport: Sentry.makeBrowserOfflineTransport(Sentry.makeFetchTransport),
    transportOptions: { maxQueueSize: 100 },
    integrations: [
      new Sentry.BrowserTracing(),
      new CaptureConsole({ levels: ['error', 'warn'] }),
      new Sentry.Replay({
        maskAllText: false,
        blockAllMedia: false
      })
    ],
    initialScope: {
      user: { email: process.env.REACT_APP_USER_EMAIL }
    },
    ignoreErrors: ['Websocket']
  })

Steps to Reproduce

  1. Build the Apache Cordova App (includes generating the source maps, uses Create React App v4.0.3)
  2. Use the Sentry CLI to create a new release in Sentry: sentry-cli releases new $RELEASE
  3. Use the Sentry CLI to inject the debug IDs to the minified source and source maps files: sentry-cli sourcemaps inject --release=$RELEASE $PATH_TO_JS_FILES
  4. Upload the minified and source maps files to Sentry: sentry-cli sourcemaps upload --no-rewrite --release=$RELEASE --wait --validate $PATH_TO_JS_FILES
  5. Deploy the release in Sentry: npx sentry-cli deploys new --release=$RELEASE --env=$ENV
  6. Finalize the release sentry-cli releases finalize $RELEASE
  7. Verify the uploaded artifacts to Sentry contain the e._sentryDebugIds=e._sentryDebugIds||{} code in the minified source files and the debug_id property in the source maps files (they do)
  8. Verify we are using the latest SDK (we do)
  9. Use the application to trigger an error.
  10. Verify the debug_meta property is present in the event’s payload (it isn’t present!)

Expected Result

  1. The debug_meta property is present in the event’s payload
  2. The source maps are applied (matched) to the stack trace.

Actual Result

We get this error:

We’ve encountered 1 problem un-minifying your applications source code!

CleanShot 2023-07-10 at 12 51 22

We are using the Sentry CLI.

The debug_meta property isn’t present in the event’s payload.

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 35 (14 by maintainers)

Most upvoted comments

Ok this seems to be a cordova project. If you want to set up sourcemaps for cordova I believe you need to use the legacy method of uploading sourcemaps: https://docs.sentry.io/platforms/javascript/sourcemaps/troubleshooting_js/legacy-uploading-methods/

Cordova doesn’t support debug IDs yet.

We’re currently working on the source maps docs for Cordova so this is a bit confusing.

Hello @AbhiPrasad, @rodolfoBee! Is there anything you’d recommend us to try to fix this issue?

@rodolfoBee, I think the only way to do this would be to eject Create React App. I’ll try to do it. Just one question, however. The issues I have seen about source-map-support are source maps mismatch in the event’s stacktrace lines. Is there someone in Sentry who can confirm if this package is present then the debug_meta isn’t sent?

Maybe these (source maps line mismatch and debug_meta not present in the event’s payload) are two different issues?

I have the same issue using the vite plugin and the latest browser SDK (7.57.0). Debug IDs are present in the minified source and source maps that are successfully uploaded, but we are getting the same “Sentry is not part of build pipeline” error when viewing the events in Sentry, and when inspecting the event JSON there is no debug_meta property sent.