-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Next.js - separate build doesn't match files #14027
Comments
Hi, unfortunately, doing separate builds is not a supported use-case for sourcemap uploading. The sourcemaps and built files need to match exactly and this is not the case when rebuilding. You may get a valid result when using a deterministic |
Thanks for the response. Not sure if I understood your comment.
I think this part is working fine. When I trigger an exception, it finds the release properly. The
|
In short: Doing separate builds is not supported. You need to build your application and upload your sourcemaps in one go. |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/browser
SDK Version
8.34.0
Framework Version
Next.js 14.2.3
Link to Sentry event
https://pistachio-x0.sentry.io/issues/6005511344/?project=4507376747937792
Reproduction Example/SDK Setup
Steps to Reproduce
Because of OOM issues, decided to split my build in 2 jobs: the one in Vercel deploys the application without uploading assets and one triggered in GHA will deploy the same version and create a release with the assets.
Things work almost perfectly: the jobs have the same build name but I can't find the right source file (check the issue link)
It is not clear why these messages are there:
release.inject
option. Will not inject release.next.config.js
Build output (GHA):
Expected Result
We were supposed to see the correct file as before duplicating the jobs. It is unclear in the docs how debug ID works and if it is possible to set that. I am already setting release name and I didn't need to use RewriteFrames in the previous setup so it is unclear why this is not working.
Thanks
Actual Result
The text was updated successfully, but these errors were encountered: