Impossible to configure auth for sentry-cli on sentry for nextjs

[rsereir]

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 package are you using?

@sentry/nextjs

SDK Version

6.19.6

Framework Version

No response

Link to Sentry event

No response

Steps to Reproduce

1. Push commit on gitlab
2. CI/CD trigger
3. yarn build

Expected Result

Build should be OK without any auth token for sentry-cli ( why sentry-cli is included in sentry nextjs ? )

Actual Result

W: Sentry CLI Plugin: Command failed: /app/node_modules/@sentry/cli/sentry-cli releases new V8ns9KjkQDtMyhaaAtVxo
W: error: API request failed
W:   caused by: sentry reported an error: Authentication credentials were not provided. (http status: 401)

[smeubank]

Build should be OK without any auth token for sentry-cli ( why sentry-cli is included in sentry nextjs ? )

Is your issue possibly related or same as this issue we are working on at the moment? #3865

[rsereir]

@smeubank Hey, thanks for your answer

It's maybe related to #3865 because if sentry-cli is moved to dev dependencies, it's solve my issue. But in #3865 nothing about authentication error on production

[smeubank]

someone from the team can have a look at it, I don't know for sure, but I would hope if removing cli from build this would become a non-top

Could you try out the beta release for V7 and let me know if that works, we want to make sure we get the right fix out

[rsereir]

@smeubank Same error with 7.0 beta 0

[msafi]

Is moving sentry-cli to devDependencies a valid workaround for this issue? I've finished setting up Sentry for my app and am being blocked by this issue, so I'm wondering if that's a valid workaround. Thanks!

[lforst]

Hi, this is a known issue we want to fix very very soon. Blocking people's next build is not ok.

For now, please set the following environment variables in your CI:

• SENTRY_ORG
• SENTRY_PROJECT
• SENTRY_AUTH_TOKEN (You can find the token here - make sure it has the project:releases scope)

More information on those settings: https://docs.sentry.io/product/cli/configuration/#to-authenticate-manually

[msafi]

@lforst Thanks for your attention to this.

The values you mentioned were already set in my Vercel configurations by the Sentry Vercel integration button.

But when I reviewed the values again, I found that the SENTRY_AUTH_TOKEN wasn't being set in the Development and Preview environments on Vercel. It's only set in production. I enabled it for Development and Preview and now the build seems to work. I also added @sentry/cli to the dev dependencies. Without it, the build complained about missing @sentry/cli 🤷

[smeubank]

thanks for helping out @lforst ! 🌮

@msafi your issue is resolved then?

[msafi]

@smeubank as far as i can tell. yes!

[rsereir]

Perfect for me too ! Thanks @lforst :)