beforeSend is not called for Fatal Exceptions on Android about sentry-kotlin-multiplatform

[marandaneto]

Thanks @Legion2 .
We'll check it and come back to you.
@buenaflor have you seen that before? or @romtsn ?

[romtsn]

Thanks @Legion2 . We'll check it and come back to you. @buenaflor have you seen that before? or @romtsn ?

no, first time seeing this. I guess we have to investigate with debugger attached to see what's going on

[Legion2]

Short question: When is the beforeSend hook supposed to be executed:

1. when the exception is thrown/catched and converted to an event, or
2. before the event is send to sentry which is possibly much later than when it was catched (possibly after application restart)?

[marandaneto]

@Legion2 before the event is sent after the event is "ready" and enriched.
It depends on the platform:
iOS is after the app is restarted
Android usually before the process dies, but it can be on restart as well.

[buenaflor]

@Legion2 hi, thanks for bringing up the issue. What kind of error are you throwing in your activity? It's definitely weird that beforeSend is not being triggered. I'm trying to reproduce this issue but it seems to be working on my end. Can you show a code sample of your activity?, just to be sure.

[Legion2]

Initially a Unable to start activity ComponentInfo {...} androidx.fragment.app.Fragment$InstantiationException: Unable to instantiate fragment ...: could not find Fragment constructor caught my attention, because it was logged to sentry and had the tag mechanism: UncaughtExceptionHandler and handled: false in sentry, however we use the above beforeSend to filter such exceptions. (Use case: We provide an sdk which is integrated in 3rd party apps, we do not want to catch all errors of the 3rd party app and send them to our sentry, because they are not actionable for us)
When I tried to reproduce this in a debug version of a demo app with a debugger attached and breakpoint set in the beforeSend hook I used error("test") to throw an exception in the onCreate of the main activity to reproduce a fatal exception. During the testing I could never trigger the breakpoint in beforeSend callback.

[buenaflor]

@Legion2 could you prepare a little demo repo that reproduces this issue?

Other than that we do not officially support using Sentry within other sdks.

[buenaflor]

Closing this due to inactivity

[Legion2]

I think this issue is related to double initialization of SentrySDK, we are using React Native Sentry SDK and Kotlin Multiplatform SDK at the same type and they both initialize the Android SDK and there by overriding each others settings.
@buenaflor I was not able to find any documentation about that case and assume that it is not supported.

[buenaflor]

@Legion2 most likely yes that's the case. and yes the SDKs are not written with these cases in mind unfortunately

[Legion2]

I found this flag today (https://docs.sentry.io/platforms/react-native/manual-setup/native-init/) and hope this will fix most of the issues we have.