Vercel: Auth token not provided causes failed deploy

[D-Pagey]

Environment

• Using Sentry Saas
• "@sentry/nextjs": "6.16.1"

Steps to Reproduce

✅ yarn build locally works fine
🛑 yarn build on Vercel fails due to auth token

Expected Result

• Successful deploy

Actual Result

Questions

• The solution is to provide an auth token via environment variables which contradicts the autogenerated comment saying not to do that

[kamilogorek]

This is some misconfiguration issue in @sentry/next setup, so moving it to appropriate repo.

[lobsterkatie]

Hi, @D-Pagey!

Sorry you're having trouble. This is curious to me. It's easily fixable but I'd like to understand it first. We automatically pick up the SENTRY_AUTH_TOKEN env variable, as you can see here, but not one with NEXT_PUBLIC at the beginning.

Where are you setting the environment variable which is causing the prefix to be added? (Or did you name it that way yourself?)

[github-actions]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

[MartinSeeler]

Just in case someone finds its way via Google here, I had the same issue. Connected Vercel and Sentry via UI and ran into this error.

It took some time to discover, that the integration has set up everything correctly, but the environment variables in Vercel were set to production only, which caused the build on preview fail.