You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. I'm successfully able to report crashes using Sentry.captureException(error); but Sentry.nativeCrash(); does not not report anything on the interface.
I've automatically linked the package using react-native link @sentry/react-native which worked fine.
I still went to the "Manual setup" section to see if something went wrong, followed the steps for the Android setup and noticed a difference in my setup. In my android/app/build.gradle i don't see apply from: 'react.gradle', instead I have apply from: 'expo.gradle' which is, according to this file, based on react.gradle.
So here's what it looks like:
My honest suggestion is, create a clean new project with react-native init and copy your code over 😅
Upgrading react-native project or ejecting expo projects is a nightmare and never works without issues in my experience.
I can't really guide you in any direction since there can be several issues and most likely most of them are not related to our SDK.
OS:
Platform:
SDK:
@sentry/react-native
: ^1.0.5react-native
version: 0.59.8Init Code:
Hi. I'm successfully able to report crashes using
Sentry.captureException(error);
butSentry.nativeCrash();
does not not report anything on the interface.I've automatically linked the package using
react-native link @sentry/react-native
which worked fine.I still went to the "Manual setup" section to see if something went wrong, followed the steps for the Android setup and noticed a difference in my setup. In my
android/app/build.gradle
i don't seeapply from: 'react.gradle'
, instead I haveapply from: 'expo.gradle'
which is, according to this file, based onreact.gradle
.So here's what it looks like:
For the rest of the setup, mine is the same as the manual setup.
I have tried the workaround proposed in this issue, unsuccessful.
The text was updated successfully, but these errors were encountered: