It doesn't show original stack trace for linked errors

Environment

How do you use Sentry? Sentry SaaS (sentry.io)

Which SDK and version? @sentry/react-native 3.2.13

Steps to Reproduce

I need to report inner error when throwing exceptions, and LinkedErrors is the solution I found. To link two error, I assigned the inner error to the cause property of the final error.

//....
finalError.cause = innerError
Sentry.captureException(finalError)

When I tested, both the higher level error and the inner error are logged to sentry, however the stack trace was minified. But if I don’t link them, the stack trace worked fine, so I think it’s a bug. Here is a mini repo to reproduce the issue. https://github.com/Yupeng-li/sentry-test

The repo is a react-native app with two simple buttons: one throws an error and another throws an error with cause property.

Please modify the DSN before running it.

Expected Result

Linked error should have original stack trace.

This is what I got when I reported the error directly. (Throw an error)

Actual Result

This is what I got when I reported the error with cause. (Throw an error with cause)

[AbhiPrasad]

This is strange, it seems that RewriteFrames doesn’t update the stacktrace here?

https://github.com/getsentry/sentry-react-native/blob/16cfa52fcae796c51d1880b2ad6d9fc73dbede59/src/js/sdk.tsx#L72

Not sure if it’s a general SDK bug, or just based on how react native sdk is configuring RewriteFrames, we need to test with a stock browser SDK app that uses LinkedErrors + RewriteFrames.

[liamjones]

@krystofwoldrich I believe it’s only working for release mode, it’s still broken in debug builds, isn’t it?