#I changed the project names in Sentry and it broke my vercel builds

1 messages · Page 1 of 1 (latest)

sterile flame
#

I figured project names were just for visual labeling purposes, but I changed my project name from some initial default sentry-javascript to dashboard-prod and it broke my vercel builds.

  1. Why does this happen, this seems like a flaw but I understand that party of the sdk is knowing which project to send the data to.
  2. My only sentry env vars are SENTRY_AUTH_TOKEN and NEXT_PUBLIC_SENTRY_DSN, neither of which specify a project name (unless its encoded in these vars). There's no SENTRY_PROJECT variable in my env vars. So I'm not sure where to begin fixing this. I tried generating new auth token and new dsn but I'm still getting the same vercel build error.

Where would the 'project or. organization slug' mentioned in the error log be set if not in env vars? I've searched the entire repo for sentry and there's about 6 config files, none of which have a hardcoded project name.

image_9.png
frank moth
#

I have the same problem. Have you come right yet?

frank moth
#

@sterile flame my build error was fixed by going through the setps on the terminal again after running this command:
npx @sentry/wizard@latest -i nextjs
The instrumentation.ts file also contains the name of the project. That is one thing I noticed that got updated that might have resolved the issue.

sterile flame
#

@frank moth I found that in one of the next config files, the org and project had been hardcoded when using the setup wizard (I think), setting them to env vars fixed it

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

org: process.env.SENTRY_ORG,
project: process.env.SENTRY_PROJECT,