Luca Forstner

@DenisBessa would you mind giving a few more details? We have E2E tests covering server actions and they are not running into this.

@mkizka Thanks for providing a repro example! It appears to be a dev mode issue. When I run a prod-build everything seems to work perfectly fine. We need to somehow...

I just realized the severity of this. Sorry for the inconvenience. I originally underestimated the impact. We will fix this asap.

Hi everybody, we just released version `7.106.1` of the SDK which should address this issue. Please try it out and feel free to let us know if the fix worked...

@avarayr Thank you very much for confirming! I highly recommend **not** putting `@sentry/nextjs` and `@sentry/node` in the external packages config. It has a non-trivial effect on cold-starts and may break...

@nbolton right. Thanks for the heads up! @meienberger Thanks again for providing the workaround. I edited your comment to point people towards upgrading the SDK. I hope that's ok!

@RisingGeek if you can attribute this to the SDK and if you could provide a reproduction example that would be amazing. (if so, please do it in a new isse)...

I think we need a reproduction example we can check out locally to properly troubleshoot this.

@mikedklein Fyi, react error boundaries are only triggered when errors are thrown during rendering. Any attached event handlers, like `onClick` do not trigger error boundaries when thrown. This is React...

All errors should definitely be mapped to source code. However, if a non-Error object is thrown (i.e. some entity that does not have a stack trace), we will create a...