@sentry/nextJS 7.93.0: incessant ERR_INVALID_URL logs on every exception captured

[oalhait]

Hi, hope this finds you all well!

I've been dealing with an issue setting up Sentry with my next.js app. Everything works correctly in Sentry, but after setting up a tunnelRoute to circumvent ad blockers, I get a bunch of Invoke Errors (screenshot attached)

Referencing the incessant TypeErrors logged in the screenshot, the url sentry wants to hit isn't propagating my orgid/projectid details correctly:

"https://o:orgid.ingest.sentry.io/api/:projectid/envelope/%3Fhsts=0"

I'm wondering if my tunnelRoute is set up incorrectly, but I'm very unsure as to what the culprit might be. I've also searched and tried a bunch of different stuff with my sentry/nextJS configs to try address this, but no luck. here's my next.config.js for reference:

/** @type {import('next').NextConfig} */
const nextConfig = {
  webpack: (config, { isServer, nextRuntime, webpack }) => {
    // Avoid AWS SDK Node.js require issue: https://github.com/aws-amplify/amplify-js/issues/11030#issuecomment-1653689367
    if (isServer && nextRuntime === "nodejs")
      config.plugins.push(new webpack.IgnorePlugin({ resourceRegExp: /^aws-crt$/ }));
    return config;
  },
};

// Injected content via Sentry wizard below

const { withSentryConfig } = require("@sentry/nextjs");

module.exports = withSentryConfig(
  nextConfig,
  {
    // For all available options, see:
    // https://github.com/getsentry/sentry-webpack-plugin#options

    authToken: process.env.SENTRY_AUTH_TOKEN,
    // Suppresses source map uploading logs during build
    silent: true,
    org: "tabbed-ai",
    project: "app-tabbed-ai",
  },
  {
    // For all available options, see:
    // https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/

    // Upload a larger set of source maps for prettier stack traces (increases build time)
    widenClientFileUpload: true,

    // Transpiles SDK to be compatible with IE11 (increases bundle size)
    transpileClientSDK: true,

    // Routes browser requests to Sentry through a Next.js rewrite to circumvent ad-blockers (increases server load)
    tunnelRoute: "/api/v1/sentry",

    // Hides source maps from generated client bundles
    hideSourceMaps: true,

    // Automatically tree-shake Sentry logger statements to reduce bundle size
    disableLogger: true,

    // Enables automatic instrumentation of Vercel Cron Monitors.
    // See the following for more information:
    // https://docs.sentry.io/product/crons/
    // https://vercel.com/docs/cron-jobs
    automaticVercelMonitors: false,
  },
);

any help/guidance would be very much appreciated. Thank you in advance!

[AbhiPrasad]

@oalhait this feels like a bug, but we need more information to be sure. Could you fill out our bug report template so we have an easier time reproducing your setup (we need versions of things and some additional context): https://github.com/getsentry/sentry-javascript/issues/new?assignees=&labels=Type%3A+Bug&projects=&template=bug.yml

Thanks!

[oalhait]

awesome, thanks! filed a ticket here