-
-
Notifications
You must be signed in to change notification settings - Fork 342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[newarch][android] Sentry.nativeCrash no longer crashes RN #4446
Comments
Hi @lovegaoshi,
We will investigate this further. What version of RN are you using? |
the latest (0.76.5). can attach a repeoducer soon if necessary. appreciate
the attention!
…On Wed, Jan 15, 2025, 8:52 AM Krystof Woldrich ***@***.***> wrote:
Hi @lovegaoshi <https://github.com/lovegaoshi>,
thank you for the message,
Sentry.nativeCrash() should still crash the app, we are not planing
deprecation of the method.
We will investigate this further.
What version of RN are you using?
—
Reply to this email directly, view it on GitHub
<#4446 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZMOVVTIBQQVIRJ6VYJ6FYL2K2G5NAVCNFSM6AAAAABVGAJILCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJTGQ2DCNJZGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
- As a part of investigation of #4446
heres the reproducer - its directly adapted from my own app, but everything in App.tsx (the entry point) are removed, with a call to Sentry.nativeCrash left. the app should immediately crash as opened. new arch log:
(process is never stopped this way) old arch log:
|
What React Native libraries do you use?
RN New Architecture
Are you using sentry.io or on-premise?
sentry.io (SaS)
@sentry/react-native SDK Version
6.5.0
How does your development environment look like?
not relevant
Sentry.init()
not relevant
Steps to Reproduce
hi! i'm not sure if this actually belongs to the RN tracker (felt more so), probably will cross post;
I actually use Sentry.nativeCrash as a way to force my app to restart to apply some settings. With the old arch it works wonderfully. With the new arch RN seems to catch it instead into softException, the app lingers but displays an empty canvas. If I have a service attached, it will keep functioning for however long the native part works. I wonder if this just means Sentry.nativeCrash should be deprecated? TIA!
Expected Result
native crash, app exits
Actual Result
instead I'm left with a blank screen with the app still lingering, since RN caught this exception.
logcat trace:
The text was updated successfully, but these errors were encountered: