Linked errors are not symbolicated (RewriteFrames and LinkedErrors are not in correct order)

[doronpr]

OS:

• Windows
• MacOS
• Linux

Platform:

• iOS
• Android

SDK:

• @sentry/react-native 5.12.0 (also reproduceble in 5.15.1)
• react-native-sentry (<= 0.43.2)

SDK version: 0.0.0

react-native version: 0.71.8

Are you using Expo?

• Yes
• No
  (reproduceable in both)

Are you using sentry.io or on-premise?

• sentry.io (SaaS)
• on-premise

[Link to issue]

---

I have the following issue:
After upgrading to sentry-react-native@5.12.0 all linked errors became unminified.
This is a big problem for us as it creates duplicate issues in Sentry.

[Description]

Steps to reproduce:

• Step 1: install version 5.12.0
• Step 2: Send error as follows:

 const e1 = new Error('inner')
 const e = new Error('TRY3', {cause: e1});
 Sentry.captureException(e, );

Actual result:
Linked frame (inner) looks like this:

 File "/index.bundle//&platform=ios&dev=true&minify=false&modulesOnly=false&runModule=true&app=org.name.sentryplain", line 101276, col 25, in ?anon_0_

[Link to issue same code w/ 5.12.0]

Expected result:

 File "app:///main.jsbundle", line 101276, col 25, in ?anon_0_

[Link to issue same code w/ 5.11.0]

[krystofwoldrich]

Hi,
thank you for the message,

there were no changes to the error frames processing in the SDK between 5.11.0 and 5.12.0.

From the examples you shared the File "app:///main.jsbundle", line 101276, col 25, in ?anon_0_ is from a Release build of your application. And File "/index.bundle//&platform=ios&dev=true&minify=false&modulesOnly=false&runModule=true&app=org.name.sentryplain", line 101276, col 25, in ?anon_0_ is from Debug build.

The Local Symbolication in Debug builds only symbolicates the first Error. -> #2118 This is to be fixed in our backlog.

If you run the application in Release build with 5.12.0 or newer the stack trace should match the one from 5.11.0.