Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Vercel: Auth token not provided causes failed deploy
See original GitHub issueEnvironment
- 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
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Errors – Vercel Docs
A list of errors provided by Vercel CLI or the REST API, with details on how they occur and how to resolve them....
Read more >REST API – Vercel Docs
Note: You still need to provide an API token through the Authorization header. Failed Authentication. If authentication is unsuccessful for a request, the...
Read more >Troubleshoot a Build – Vercel Docs
Access Functions and Building Logs view from the Deployment page. Troubleshoot Build failures. If your build fails, the related error is reported in...
Read more >Application Authentication on Vercel
Authentication verifies a user's identity to provide access to your application. When adding authentication to your serverless application, you'll likely ...
Read more >Vercel API
When building an integration with Vercel, you can request Vercel Access Tokens to authenticate and use the Vercel API. You must provide an...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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.
Docs should be updated to make this clear. Will update if I find time and no one else has gotten around to it by then.