Multiple tracking.enable$argument_0.onUnhandled error reported

[elmotan95]

OS:

• Windows
• MacOS
• Linux

Platform:

• iOS
• Android

SDK:

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

SDK version: 5.5.0

react-native version: 0.69.10

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: 'redacted',
    enableAutoSessionTracking: true,
    environment: config.environment,

    ignoreErrors: [
      // Axios throw error from createError.js, please see useFetch for error log
      /Request\sfailed\swith\sstatus\scode.*/,
      // react-native-fingerprint-scanner
      /.*biometric.*/,
      // appsflyer
      /.*inapps\.appsflyer\.com.*/,
      /.*com\.appsflyer\.sdk\.network.*/,
    ],

    integrations: [
      new Sentry.ReactNativeTracing({
        enableUserInteractionTracing: true,
        routingInstrumentation,
        shouldCreateSpanForRequest: url => {
          const urlRedacted = /redacted/;
          const urlLocalhost = /localhost/;

          return !url.match(urlRedacted) && !url.match(urlLocalhost);
        },
        // ... other options
      }),
    ],

    sampleRate: 0.2,
    // Sessions close after app is 10 seconds in the background.
    sessionTrackingIntervalMillis: 10000,
    tracesSampleRate: 0.2,
  });

---

I have following issue:

[Description]

I saw issue being logged on Sentry that related to error reporting. Not sure what caused this issues.

tracking.enable$argument_0.onUnhandled

Actual result:

[Actual result]

Expected result:

No issues related to sentry reported

[krystofwoldrich]

Hi,
thank you for the message,
could you share more about the error, are there any breadcrumbs, are there more frames in the stack trace?

[isinuyk]

@krystofwoldrich @elmotan95
Got the same problem on the newly released version of the app.
For me, it is IOS only.

"@sentry/react-native": "^5.4.1",
"react-native": "0.71.7",

[krystofwoldrich]

@isinuyk Thank you for the information, are you able to reproduce it locally, from the message I assume not, but I want to double-check?

[isinuyk]

@isinuyk Thank you for the information, are you able to reproduce it locally, from the message I assume not, but I want to double-check?

No. I'm not able to reproduce it in debug mode. Only happens on the release version of the app;

[elmotan95]

Hi, thank you for the message, could you share more about the error, are there any breadcrumbs, are there more frames in the stack trace?

Nope. Data form breadcrumbs does not provide any relevant information (it's only API call with status 200 and screen name). And it does not happened on development apps.

[krystofwoldrich]

@isinuyk Since you mentioned it's iOS only, could it be incorrect source maps causing the issue, are your other iOS JS errors source mapped correctly?

[isinuyk]

@isinuyk Since you mentioned it's iOS only, could it be incorrect source maps causing the issue, are your other iOS JS errors source mapped correctly?

I don't think so. It is an example of another issue within the same release which has the correct source map

[NiharR27]

+1 Seeing this on "@sentry/react-native": "^5.7.1" with RN "0.71.12"

This seems to have somehow started after I enabled one of the options here:

Sentry.init({
    dsn: XXXXXXXX,
    environment: XXXXXXXX,
    integrations: [
      new Sentry.ReactNativeTracing({
        tracingOrigins: [XXXXXXXX, /^\//],
        routingInstrumentation,   ===============> NEWLY ADDED THIS
      }),
    ],
    beforeBreadcrumb: (breadcrumb, hint) => {  ===============> NEWLY ADDED this (beforeBreadcrumb function)
      if (['http', 'fetch', 'xhr'].includes(breadcrumb.category))
        return { ...breadcrumb, data: hint };
      return breadcrumb;
    },
    tracesSampleRate: 0.4,
    attachScreenshot: true, ===============> NEWLY ADDED this
  });

on release build.

It is also only happening on iOS devices as mentioned in other comments

cc @abandisch just tagging you here

[krystofwoldrich]

@NiharR27 Thank you for the information, would you be able to narrow it down? Or share a minimal reproducible example?

[NiharR27]

@NiharR27 Thank you for the information, would you be able to narrow it down? Or share a minimal reproducible example?

@krystofwoldrich sure, i will try to replicate once I get to the office tomorrow. Additionally, I have also updated the last comment to mention what changes we made recently before pushing (after which the above started)

[NiharR27]

Still trying to replicate this on release build (when building on my local device).
Here are sentry log however:

Note: I have hermes enabled. on iOS only.

I have noticed this happening during the app startup (at-least that's what i see in the screenshot that the sentry shows)

Noticed this on iPhone 11 , iPhone 8 Arch:arm64 iOS Version:16.6 (from the error logs that we been getting). and it is handled (not crashing the app).

I will post something in this post, in-case i find more / able to replicate

[isinuyk]

The interesting thing is that right after I made a codepush to the affected by this problem latest IOS release the title and traces for this issue changed a bit. Now it looks like:

[krystofwoldrich]

@isinuyk This stack trace looks correct since there was no stack trace with the original error Sentry captures synthetical error at the time to show the current stack trace.

[Bardiamist]

Same problem, 4 users, 5 events

Error: [{}]
  at tracking.enable$argument_0.onUnhandled(node_modules/@sentry/react-native/dist/js/integrations/reactnativeerrorhandlers.js:85:57)
  at onUnhandled(node_modules/promise/setimmediate/rejection-tracking.js:73:25)
  at apply(native)
  at setTimeout(node_modules/react-native/Libraries/Core/Timers/JSTimers.js:213:35)
  at _callTimer(node_modules/react-native/Libraries/Core/Timers/JSTimers.js:113:15)
  at callTimers(node_modules/react-native/Libraries/Core/Timers/JSTimers.js:359:30)
  at apply(native)
  at __callFunction(node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:428:32)
  at __guard$argument_0(node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:113:43)
  at __guard(node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:367:7)
  at callFunctionReturnFlushedQueue(node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:112:18)

[ts-ign0re]

Same problem guys

[krystofwoldrich]

@ts-ign0re Thanks for the info, were you able to reproduce it locally? Does it happen on both iOS and Android? Are other errors symbolicated correctly?

[MarkHaakman]

For me it also happens on Android.
8 users with 291 events. RN 0.71.13, Sentry 5.9.1.
I could not reproduce it locally.

[krystofwoldrich]

@Kowaio Thank you for the information, we will keep you posted on any updates regarding this issue.

[lucasftcruz]

Facing the same issue on iOS. For us started coincidentally when we updated RN 0.70.9 to 0.70.13. I'm not able to reproduce the issue and can confirm it only happens on release builds

"react-native": "^0.71.14",
"@sentry/react-native": "^5.4.0",

[krystofwoldrich]

@lucasftcruz The stack trace you shared looks correct, you can ignore the first frame pointing to Sentry, that's present because we report the unhandled Promise rejection.

[savv]

We are also seeing this error on iOS right after Codepush installs a bundle and it causes the app to crash. We can replicate this ~50% of the time on one of our devices by a) freshly installing the app b) selecting "Install" on the Codepush prompt*. Skipping b) means that the app does not crash. I am not sure if this is caused by Sentry, but I thought I would report my findings.

The stack trace, which similar to the above seems to start here:

1. in callFunctionReturnFlushedQueue
2. Then this invariant seems to trigger in line 428: Failed to call into JavaScript module method ${module}.${method}(). Module exists, but the method is undefined.
   This would further suggest that it's related to Codepush. For example, Codepush invalidates all RCTBridges when it restarts (which happens when a new bundle is installed.)

The one thing that doesn't fit the above, is that I don't see this error message anywhere. Maybe invariant is not creating the error in a way that is compatible with sentry. Maybe "Error: 1" comes from here?

* Our codepush config checks for updates when the app starts, and asks the user whether they want to upgrade; if you press "Install", we install the new bundle immediately. Config: {checkFrequency: codePush.CheckFrequency.ON_APP_RESUME, installMode: codePush.InstallMode.IMMEDIATE,updateDialog: {}}

[krystofwoldrich]

@savv Thank you for the detailed findings.

[savv]

@savv Thank you for the detailed findings.

reactnativeerrorhandlers.ts seems to polyfill Promises, in order to catch unhandled promise rejections, but I wasn't able to trigger that code.

When does onUnhandled ever execute? How can I get it to?

[krystofwoldrich]

The onUnhandled get triggered on unhandled promise rejection.

The SDK reports that there was unhandled rejected promise, but the top of the stack should exclude the Sentry frame.

[savv]

The onUnhandled get triggered on unhandled promise rejection.

The SDK reports that there was unhandled rejected promise, but the top of the stack should exclude the Sentry frame.

I see, so as invariant sets error.framesToPop = 1; maybe there's a bug in addGlobalEventProcessor / parseErrorStack or it's incompatible with Sentry's promise handling. Although I wasn't able to replicate it.

[krystofwoldrich]

@savv Thank you, we'll investigate it.

[savv]

As a final FYI, I also just saw that RN 0.72.7 includes the following fix:

Show correct stack frame on unhandled promise rejections on development mode.
facebook/react-native@18c9797

While I didn't look at the code it could be related. Thanks again

[birgernass]

@savv were you able to get to the bottom of the Error: 1 issue? We see these events very frequently since upgrading to 5.15.x from a 5 alpha version.

[rodolfoBee]

Reopening issue as users are getting these reports in the newest versions of the SDK. The issue does not seem to be caused by the SDK, it is simply being reported by it.

@krystofwoldrich can you please confirm it from the Mobile SDK team side?

[ts-ign0re]

If you encounter this problem, try to find the following line in your code or in the code of the libraries you use

return Promise.reject();

my case was due to the similar use of Promise, which caused onUnhandled

This is not a Sentry bug, however Sentry does not handle Promise correctly and does not indicate in which line the unhandled promise occurred

[krystofwoldrich]

@rodolfoBee I can confirm, this is not an issue caused by the SDK. The SDK just captures a Promise rejection without any additional information, without a stack trace attached.

This can happen for example when Promise.reject() is called without an error instance. Like @ts-ign0re mentioned.