Invalid source maps

[Sothatsit]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/browser

SDK Version

8.30.0

Framework Version

14.2.13

Link to Sentry event

https://royalur.sentry.io/share/issue/b4f6cc2c5cce4dc6bd94d8e9755b79c7/

Reproduction Example/SDK Setup

withSentryConfig:

withSentryConfig(config, {
    org: "royalur",
    project: "javascript-react",
    release: {
        name: gitCommitHash,
        inject: true,
    },
  
    authToken: process.env.SENTRY_AUTH_TOKEN,
  
    silent: false,
    telemetry: false,
  
    // Transpiles SDK to be compatible with IE11 (increases bundle size)
    transpileClientSDK: true,
  
    // Hides source maps from generated client bundles
    hideSourceMaps: true,
  
    // Automatically tree-shake Sentry logger statements to reduce bundle size
    disableLogger: true,
  
    // We were getting an error with the URIs being too long.
    dedupe: false,
});

sentry.client.config.ts:

// This file configures the initialization of Sentry on the client.
// The config you add here will be used whenever a users loads a page in their browser.
// https://docs.sentry.io/platforms/javascript/guides/nextjs/

import * as Sentry from "@sentry/nextjs";

Sentry.init({
    dsn: "https://1f280a721de7d8c998aeda1123a228a3@o4507083546361856.ingest.us.sentry.io/4507083549179904",

    // Adjust this value in production, or use tracesSampler for greater control
    tracesSampleRate: 1,

    // Setting this option to true will print useful information to the console while you're setting up Sentry.
    debug: false,

    replaysOnErrorSampleRate: 1.0,

    // This sets the sample rate to be 10%. You may want this to be 100% while
    // in development and sample at a lower rate in production
    replaysSessionSampleRate: 0.1,

    // You can remove this option if you're not planning to use the Sentry Session Replay feature:
    integrations: [
        Sentry.replayIntegration({
            // Additional Replay configuration goes in here, for example:
            maskAllText: true,
            blockAllMedia: true,
        }),
    ],
});

Steps to Reproduce

1. Run build within Docker container.
2. Release and source maps are uploaded.
3. Issue is created from production website.
4. The issue is not able to associate the stack trace with source maps.

I also attempted to enable debug printing to log any Sentry errors, and there were none. There was just a lot of information about Sentry uploading source maps for Node.js, Edge, and Client.

Expected Result

The source maps should be available within issues.

Actual Result

The source maps are not available for most lines in stack traces. They are very rarely available for single lines though.

Issues within my Sentry dashboard expect sourcemaps to be associated with the chunks that NextJS has generated, such as: app:///_next/static/chunks/7073-02a6ef3696be4a11.js

However, the sourcemaps that are uploaded with my release do not match these chunks. Instead, three bundles of sourcemap artifacts are uploaded with names like ~/002de75e-b678-43f3-917c-12c2d70c7705-69.js.map

[lforst]

Hi, can you try the widenClientFileUpload option? Thanks! https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/#widen-the-upload-scope

[Sothatsit]

It appears that this has worked, thank you!

I had previously enabled this option, and at that time it didn't fix the issue. But maybe something else I have changed since then has now made it work. The only thing I remember changing was the release.inject and dedupe options, but it could be something else.

Regardless, thank you for the help.