Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

with-sentry-simple requires auth to upload sourcemaps via webpack plugin #12314

Closed
leonclaus opened this issue Apr 29, 2020 · 1 comment · Fixed by #12316
Closed

with-sentry-simple requires auth to upload sourcemaps via webpack plugin #12314

leonclaus opened this issue Apr 29, 2020 · 1 comment · Fixed by #12316

Comments

@leonclaus
Copy link
Contributor

leonclaus commented Apr 29, 2020

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

  1. Pull with-sentry-simple repository
  2. Specify SENTRY_DSN, SENTRY_ORG, SENTRY_PROJECT environment variables
  3. Run with now dev
  4. See error

Expected behavior

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.

@balazsorban44
Copy link
Member

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 vercel locked as resolved and limited conversation to collaborators Jan 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants