You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Sentry configuration as specified in with-sentry-simple, the Sentry CLI (used in @sentry/webpack-plugin) responds with the following: sentry-cli.exe releases new ... error: API request failed caused by: sentry reported an error: Authentication credentials were not provided. (http status: 401)
The exact versions specified in the example were used. The issue was tested locally via now dev.
Sourcemaps are supposed to be sent to Sentry via the webpack plugin.
System information
OS: Windows
Browser: Chrome
Version of Next.js: 9.3.4
Version of Node.js: 12.14.1
Version of @sentry/webpack-plugin: 1.10.0 (also tested with newer version)
Version of @zeit/next-source-maps: 0.0.4-canary.1
Additional context
I fixed the issue by specifying the SENTRY_AUTH_TOKEN environment variable and creating a custom integration in sentry in #12316. However I am unsure whether this is an optimal solution.
The text was updated successfully, but these errors were encountered:
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.
vercel
locked as resolved and limited conversation to collaborators
Jan 30, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug report
Describe the bug
When using Sentry configuration as specified in with-sentry-simple, the Sentry CLI (used in @sentry/webpack-plugin) responds with the following:
sentry-cli.exe releases new ... error: API request failed caused by: sentry reported an error: Authentication credentials were not provided. (http status: 401)
The exact versions specified in the example were used. The issue was tested locally via
now dev
.To Reproduce
now dev
Expected behavior
Sourcemaps are supposed to be sent to Sentry via the webpack plugin.
System information
Additional context
I fixed the issue by specifying the SENTRY_AUTH_TOKEN environment variable and creating a custom integration in sentry in #12316. However I am unsure whether this is an optimal solution.
The text was updated successfully, but these errors were encountered: