Closed bjornevik closed 8 months ago
It's possible that one or more of the other packages you have installed is conflicting with this one, which could be an explanation for why it works on a clean app and not on yours. You could try a resolution for expo-modules-core
and see if that addresses it. If not, then if you can include a minimal reproducible example I can investigate it some more.
Finally made some progress, seems like the RNSentry.fetchNativeAppStart
wasn't a red herring after all. It seems to be working after removing @sentry/react-native
and sentry-expo
.
Seeing as sentry-expo
has been merged into @sentry/react-native
and been deprecated as of SDK 50, that might be the problem. I'll keep troubleshooting - hopefully I'll be able to pinpoint the issue.
The crash only happens if I set the tracesSampleRate
parameter in the Sentry.Init({ /* ... */})
call. Unsure why. Nonetheless seems like it's a Sentry issue and not a issue with this package. I've opened an issue in the sentry-react-native repo, and I'll close this issue since I got it working.
Hi i'm having a problem with android production builds building fine, but when running them on a device it crashes after the splash screen. I'm having the same problem when running android development builds with the
--no-dev
flag.This only happens when I install this package, even if I don't use it, and I'm not able to recreate it with a clean create-expo-app project.
The initial error I'm shown is a
Invariant Violation: "main" has not been registered
^mainnotregistered error. The fatal error I'm getting when running withadb logcat
is the following, which I believe is a red herring:Furthermore I also find the following error in
adb logcat
The only references to
viewManagersMetadata
I can find is in the following packages:expo-modules-core
,expo-dev-menu
,expo-dev-launcher
. Seeing asexpo-modules-core
is the only dependency this package uses I'm guessing the problem is related to it, but once again, because it works fine on a clean create-expo-app project I don't know.Also found a NullPointerException in
adb logcat
, but I'm suspecting it's related to theexpo-updates
red herring.I'm at wits end, the only idea I have is to upgrade the expo-modules-core dependency in this project, but I logically don't see how that would help when it runs fine on a clean create-expo-app project.
Any ideas? I've been stuck with this for a week.