Unhandled promises are not logged at all (iOS and Android)

[lukewlms]

Platform:

• iOS

SDK:

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

SDK version: "@sentry/react-native": "^1.7.2",

react-native version: "react-native": "^0.63.2",

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:

No issue was created

Configuration:

(@sentry/react-native)

Sentry.init({
  dsn: 'https://...@sentry.io/...'
  // no extra options
});

---

I have following issue:

Normal exceptions are logged to Sentry.io just fine, but unhandled promises are not logged at all. My understanding is that this should happen by default. I do get a yellow box showing the unhandled exception but it seems that Sentry never sees it.

This repros on both Android and iOS.

Steps to reproduce:

1. Install sentry with minimal config
2. Generate an unhandled promise rejection

Actual result:

Yellow box appears but no error logged to sentry.io

Expected result:

Unhandled promise rejections are logged to sentry.io

[azai91]

Having the same issue.

[WinstonKamau]

I am also experiencing the same issue for unhandled promises.

[cruzach]

I think that this is due to the same issue as this- facebook/fbjs#413 (mismatch of promise versions)

[jer-sen]

@cruzach you are right but its a big issue since it makes sentry nearly useless!
With Expo you can add this to your package.json as a workaround until fbjs dependencies are upgraded:

  "resolutions": {
    "expo/**/promise": "^8.0.3"
  },

@cruzach maybe sentry should hook itself directly on Promise global object as promise/setimmediate/rejection-tracking does and instead of using it. It would avoid the issue to reappear. Or add to the doc that there must be only one version of promise module per project.

[stevefai]

Is this working for anybody right now with the latest versions? Just created a brand new react native project and running into the same issue.

[Baloche]

Same issue here with the latest versions. I am currently using @jer-sen's workaround and it works !

[jennmueng]

I have reproduced the issue and confirmed that unhandled promise rejections are not being caught on my end as well. Adding this to our immediate TODO.