Event exception stacktrace selected frame (0) has incorrect abs_path (valid url is required). Found native

[Eden-Eliel]

OS:

• Windows
• MacOS
• Linux

Platform:

• iOS
• Android

SDK:

• @sentry/react-native (>= 1.0.0)
• react-native-sentry (<= 0.43.2)

SDK version: 5.2.0

react-native version: 0.70.5

Are you using Expo?

• Yes
• No

Are you using sentry.io or on-premise?

• sentry.io (SaaS)
• on-premise

If you are using sentry.io, please post a link to your issue so we can take a look:

Link to issue

Configuration:

(@sentry/react-native)

Sentry.init({
      dsn: config.SENTRY_DSN,
      release: getVersion(),
      dist: getBuildNumber(),
      environment: config.ENV_NAME === "Production"
          ? "production"
          : "qa",
      integrations: [
          new Sentry.ReactNativeTracing({
              routingInstrumentation
          }),
      ],
});

---

I have following issue:

Hey,
I'm trying to get the iOS on our app to work with source maps, however, I encounter some errors when trying to look at the error.
The output of the explain of this:

✔ Fetched data for event: a257684de1db4630b69475cc212bba02
✔ Event has release name: 7.2.3
✔ Event has a valid exception present
✔ Event has a valid stacktrace present
✖ Event exception stacktrace selected frame (0) has incorrect abs_path (valid url is required). Found native

I assume it relates to some issues mentioned here:
#2891
#2683 (comment)

One of the frames in the issue is:
{"function":"apply","filename":"native","abs_path":"native","in_app":true}

which I assume is the cause of this issue, but I thought the new version (5.2.0) should fix it.
Any suggestion?

Actual result:

✔ Fetched data for event: a257684de1db4630b69475cc212bba02
✔ Event has release name: 7.2.3
✔ Event has a valid exception present
✔ Event has a valid stacktrace present
✖ Event exception stacktrace selected frame (0) has incorrect abs_path (valid url is required). Found native

Expected result:

✔ Fetched data for event: 091e863ca2724cb6995b030e65e918ec
✔ Event has release name: 7.2.3
✔ Event has a valid exception present
✔ Event has a valid stacktrace present
⚠ Exception is already source mapped and first resolved frame points to:

                       handleComponent={handleComponent}
                       onAnimate={onSheetAnimate}
                       {...props}
          >
              <RectButton onPress={() => {
>                 throw new Error("Some Flaysh Error!!!")
              }}>
                  Eden
              </RectButton>
              <RectButton onPress={() => {
                  JSON.parse("Flaysh")

Thanks ahead, Eden.

[Eden-Eliel]

Update:
I have tried to change the abs_path just to check if it would give other issue:

if (frame.abs_path === 'native') {
    frame.abs_path = '[native-code]'
}

Event exception stacktrace selected frame (0) has incorrect abs_path (valid url is required). Found [native-code]

so it's absolutely this frame.
I suspect that with one of the integrations if the abs_path is missing (after the delete frame.abs_path) it will add it anyway. (Alone the integration works fine)

[Eden-Eliel]

Another Update:
i have made an integration that will override the native abs_path so it will not fail:

integrations: [
                    new RewriteFrames({
                        iteratee: (frame) => {
                            if (frame.filename) {
                                frame.filename = frame.filename
                                    .replace(/^file:\/\//, '')
                                    .replace(/^address at /, '')
                                    .replace(/^.*\/[^.]+(\.app|CodePush|.*(?=\/))/, '');
                                if (frame.filename !== '[native code]' &&
                                    frame.filename !== 'native') {
                                    const appPrefix = 'app://';
                                    // We always want to have a triple slash
                                    frame.filename =
                                        frame.filename.indexOf('/') === 0
                                            ? `${appPrefix}${frame.filename}`
                                            : `${appPrefix}/${frame.filename}`;
                                    delete frame.abs_path;
                                }
                            }

                            if (frame.abs_path === 'native') {
                                frame.abs_path = isIos ? 'app:///main.jsbundle' : 'app:///index.android.bundle';
                            }
                            return frame
                        }
                    }),
                    new Sentry.ReactNativeTracing({
                        routingInstrumentation
                    }),
                ],

And this is my result now:

✔ Fetched data for event: 25bdc397551c4b05a3dbdb45faef7a9a
✔ Event has release name: 7.2.3
✔ Event has a valid exception present
✔ Event has a valid stacktrace present
⚠ Exception is already source mapped and first resolved frame points to:

> [missing context line]

seems like something that was mentioned here but in react native we are not using webpack

following command on generating sourcemap (iOS), which as i understand do not need the .hbc.map thing:

node_modules/.bin/react-native bundle \
  --dev false \
  --platform ios \
  --entry-file index.js \
  --bundle-output sourcemaps/ios/main.jsbundle \
  --sourcemap-output sourcemaps/ios/main.jsbundle.map \
  --minify false

Hope it helps figure out my issue.

[krystofwoldrich]

Thank you for all the details, we will take a look into it.

[krystofwoldrich]

The reason why you get > [missing context line] after applying your fix is that you trying to process the native code stack trace frame as it would be js code. Only the JS frames can be mapped.

I've checked the mentioned event ✔ Fetched data for event: a257684de1db4630b69475cc212bba02 its tagged release:7.2.3, but this release has no source maps artifacts. Can you check your build logs that the source maps are uploaded or upload the source maps manually?

[Eden-Eliel]

The reason why you get > [missing context line] after applying your fix is that you trying to process the native code stack trace frame as it would be js code. Only the JS frames can be mapped.

I've checked the mentioned event ✔ Fetched data for event: a257684de1db4630b69475cc212bba02 its tagged release:7.2.3, but this release has no source maps artifacts. Can you check your build logs that the source maps are uploaded or upload the source maps manually?

Thanks for the replay,
Yea it makes sense because I always removed the sourcemaps haha.

However, I used the automatic upload and everything looks fine.

If you want to keep it and try to figure out why it happened, I can upload everything manually again, I don't mind.

Lemme know if you want to close it, or keep investigating the manual upload