Luca Forstner

If possible a reproduction would be amazing to sustainably fix this.

`@sentry/nextjs` needs export conditions to work. We ship multiple versions of the SDK for the different runtimes (browser/node/edge) and we use export conditions to determine which SDK should be loaded....

I don't think this is solvable from within the SDK as it has more to do with consuming tooling and configuration. If anybody has a suggestion on what we could...

Hi, sorry for the wait. The reproduction repo is private so I cannot look at it, but I am still gonna try to be useful here. As a first step...

@anyulled Please check our guide on how to combine Sentry with your own opentelemetry setup: https://docs.sentry.io/platforms/javascript/guides/node/opentelemetry/custom-setup/ Seems like you didn't do that from looking at your setup.

@linxiaowang since we can never fully be sure when a page is "done loading" we are using a set of heuristics to terminate the transaction when we don't see any...

The `idleTimeout` is the timeout that finishes the transaction when there is no active span. The heartbeat is a timeout that finishes the transaction when the span count doesn't change...

Hi, would you mind sharing a small reproduction example we could clone to check this error out? It is usually quite hard to troubleshoot build errors without having access to...

Hi @webdevian and @baw! It would be amazing if you could share a small reproduction example where this is happening.

Can somebody share reproduction? Thanks!