[Question/Bug] Early exceptions are not send to sentry and deleted on the app restart

[ppeszko]

OS:

• Windows
• MacOS
• Linux

Platform:

• iOS
• Android

Output of node -v && npm -v && npm ls --prod --depth=0

v11.3.0
6.4.1
ReactNativeSentryMissingExceptionsProject@0.0.1 /Users/projects/ReactNativeSentryMissingExceptionsProject
├── react@16.6.1
├── react-native@0.57.7
└── react-native-sentry@0.40.2

Config:

Sentry.config('https://51e610c7477a4363af4ccfd9517e0bdb@sentry.io/1352206').install();

---

I have following issue:

If an app throws an exception really early in the lifecycle (https://github.com/ppeszko/ReactNativeSentryMissingExceptionsProject/blob/master/App.js#L27) this exception will be never reported to the sentry backend. The exception will be recorded, and you can confirm it by downloading the app bundle:

But on the app restart the exception will be deleted/rejected by the following code:

https://github.com/getsentry/react-native-sentry/blob/master/ios/RNSentry.m#L140

The comment in the above line is a well a bit confusing as it would suggest that the exception was handled ('we sent it already before the app crashed') but in fact, it wasn't.

Our question is:

• is this something which is a known issue and won't be addressed?
• is there a way to be able to see all exceptions in sentry?

Steps to reproduce:

• Check out the demo project: https://github.com/ppeszko/ReactNativeSentryMissingExceptionsProject
• Start the app

Expected result:

• All exceptions are reported to sentry backend so they can be fixed

[HazAT]

Thanks for the repro case, this is actually a bug I would say.
Not sure when we are able to fix it though but we are aware of it now.

[ppeszko]

thank you checking it @HazAT 🙇 :)

[marandaneto]

still happens on the latest Sentry RN version, since the App crashes immediately, the iOS SDK doesn't have time to send it, only on iOS tho.

[marandaneto]

since this is an issue with the iOS SDK only and requires more discussion on how to tackle this, I've transferred to the iOS repo, we'll follow up on this.

[philipphofmann]

Is a duplicate of #316