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

Eden-Eliel · 2023-03-23T22:52:16Z

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.

The text was updated successfully, but these errors were encountered:

Eden-Eliel · 2023-03-24T01:41:20Z

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 · 2023-03-24T03:28:35Z

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 · 2023-03-24T11:32:48Z

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

krystofwoldrich · 2023-03-24T16:56:06Z

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 · 2023-03-24T18:32:51Z

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

krystofwoldrich · 2023-03-27T08:58:18Z

@Eden-Eliel Okay, that makes sense, could you upload the source maps (and keep them) and send us a link to a new error?

krystofwoldrich · 2023-04-12T09:29:29Z

Closing this due to inactivity. If this is still an issue feel free to comment here or open a new issue if the context changed.

dmregister · 2023-05-04T15:38:26Z

@krystofwoldrich we are having the same issue with sourcemaps not being applied errors. Here is the output of the explain command:

✔ Fetched data for event: 123
✔ Event has release name: ###@#.#.#+407600003
✔ 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

The only thing that changed was we updated our packages from 5.1.1 to 5.3.1. When I downloaded the arifacts and re-uploaded them using the same cmds but with the latest CLI, I am not seeing the source maps being applied to new events.

krystofwoldrich · 2023-05-05T11:43:08Z

@dmregister Can you try this with the latest SDK version, https://github.com/getsentry/sentry-react-native/releases/tag/5.4.1? Could you share the raw stack trace?

dmregister · 2023-05-05T11:56:44Z

I did just update to 5.4.1 and I think I saw it was corrected. I updated after I saw this issue: #3010

Here is the raw stack:

Error: Unexpected token T in JSON at position 376
  at call(native)
  at ApolloError(app:///index.android.bundle:1:1866725)
  at anonymous(app:///index.android.bundle:1:1880512)
  at anonymous(app:///index.android.bundle:1:1882040)
  at anonymous(app:///index.android.bundle:1:1881451)
  at anonymous(app:///index.android.bundle:1:1874776)
  at useDeepMemo(app:///index.android.bundle:1:1874106)
  at useBaseQuery(app:///index.android.bundle:1:1874566)
  at useQuery(app:///index.android.bundle:1:1875270)
  at useExampleQuery(app:///index.android.bundle:1:4708754)
  at ExampleProvider(app:///index.android.bundle:1:6768839)
  at renderWithHooks(app:///index.android.bundle:1:306544)
  at updateForwardRef(app:///index.android.bundle:1:311595)
  at beginWork$1(app:///index.android.bundle:1:347667)
  at performUnitOfWork(app:///index.android.bundle:1:334914)
  at workLoopSync(app:///index.android.bundle:1:334771)
  at renderRootSync(app:///index.android.bundle:1:334655)
  at performSyncWorkOnRoot(app:///index.android.bundle:1:332071)
  at flushSyncCallbacks(app:///index.android.bundle:1:296448)
  at scheduleUpdateOnFiber(app:///index.android.bundle:1:328974)
  at dispatchReducerAction(app:///index.android.bundle:1:309853)
  at tryCallOne(app:///index.android.bundle:1:357378)
  at anonymous(app:///index.android.bundle:1:358054)
  at apply(native)
  at anonymous(app:///index.android.bundle:1:369752)
  at _callTimer(app:///index.android.bundle:1:368701)
  at _callReactNativeMicrotasksPass(app:///index.android.bundle:1:368865)
  at callReactNativeMicrotasks(app:///index.android.bundle:1:370845)
  at __callReactNativeMicrotasks(app:///index.android.bundle:1:271417)
  at anonymous(app:///index.android.bundle:1:270509)
  at __guard(app:///index.android.bundle:1:271258)
  at flushedQueue(app:///index.android.bundle:1:270420)
  at invokeCallbackAndReturnFlushedQueue(app:///index.android.bundle:1:270363)

krystofwoldrich · 2023-05-08T08:40:49Z

@dmregister So just to double-check with the 5.4.1 the stack traces are symbolicated correctly?

dmregister · 2023-05-08T18:12:46Z

@krystofwoldrich yes it did, thanks for following up.

Eden-Eliel added the Platform: React-Native label Mar 23, 2023

getsantry bot added the Status: Untriaged label Mar 23, 2023

krystofwoldrich removed the Status: Untriaged label Mar 24, 2023

krystofwoldrich added this to [DEPRECATED] Mobile SDKs Mar 24, 2023

krystofwoldrich moved this to Needs Investigation in [DEPRECATED] Mobile SDKs Mar 24, 2023

krystofwoldrich added the Type: 🪲 Bug label Mar 24, 2023

marandaneto assigned krystofwoldrich Mar 24, 2023

krystofwoldrich moved this from Needs Investigation to Needs More Information in [DEPRECATED] Mobile SDKs Mar 24, 2023

krystofwoldrich added Status: Awaiting Response and removed Type: 🪲 Bug labels Mar 24, 2023

krystofwoldrich closed this as not planned Won't fix, can't repro, duplicate, stale Apr 12, 2023

github-project-automation bot moved this from Needs More Information to Done in [DEPRECATED] Mobile SDKs Apr 12, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

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

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

Eden-Eliel commented Mar 23, 2023

Eden-Eliel commented Mar 24, 2023

Uh oh!

Eden-Eliel commented Mar 24, 2023 •

edited

Loading

Uh oh!

krystofwoldrich commented Mar 24, 2023

Uh oh!

krystofwoldrich commented Mar 24, 2023

Uh oh!

Eden-Eliel commented Mar 24, 2023

Uh oh!

krystofwoldrich commented Mar 27, 2023

Uh oh!

krystofwoldrich commented Apr 12, 2023

Uh oh!

dmregister commented May 4, 2023 •

edited

Loading

Uh oh!

krystofwoldrich commented May 5, 2023 •

edited

Loading

Uh oh!

dmregister commented May 5, 2023

Uh oh!

krystofwoldrich commented May 8, 2023

Uh oh!

dmregister commented May 8, 2023

Uh oh!

Uh oh!

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

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

Comments

Eden-Eliel commented Mar 23, 2023

Eden-Eliel commented Mar 24, 2023

Uh oh!

Eden-Eliel commented Mar 24, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

krystofwoldrich commented Mar 24, 2023

Uh oh!

krystofwoldrich commented Mar 24, 2023

Uh oh!

Eden-Eliel commented Mar 24, 2023

Uh oh!

krystofwoldrich commented Mar 27, 2023

Uh oh!

krystofwoldrich commented Apr 12, 2023

Uh oh!

dmregister commented May 4, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

krystofwoldrich commented May 5, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dmregister commented May 5, 2023

Uh oh!

krystofwoldrich commented May 8, 2023

Uh oh!

dmregister commented May 8, 2023

Uh oh!

Eden-Eliel commented Mar 24, 2023 •

edited

Loading

dmregister commented May 4, 2023 •

edited

Loading

krystofwoldrich commented May 5, 2023 •

edited

Loading