-
Notifications
You must be signed in to change notification settings - Fork 83
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
Sentry Logger [Warn]: SentryError: Native is disabled #243
Comments
I experienced the same issue after upgrading SDK 41 to 44. How to fix it?
|
While using Expo SDK 44, I was able to get things working with sentry-expo v4.0.0 and @sentry/react-native v2.5.2 It's unideal since I'm losing some Sentry functionality but at least Sentry is able to capture native events now. Hopefully the latest version of sentry-expo will work with Expo SDK 44 soon |
our stack traces look different from those by @lavender16 above, but the issue seems similar. I was sure to do the package install using "yarn expo install sentry-expo". Errors and messages do create new Sentry issues. Sentry Logger [Warn]:, [SentryError: Native is disabled] Sentry Logger [Warn]:, [SdkInfo] Native SDK Info retrieval failed...something could be wrong with your Sentry installation: |
I'm seeing the same error. And I don't know if it's related, but I'm not seeing any stack traces in Sentry. I'm also using Expo SDK 44, and can confirm that this is still happening when you follow the directions for installing |
I am also in the exact same situation as @ajenkins . Can we please get some insight on this issue |
We're running into the same issue. Would be great to have some update on this. Currently this is rendering sentry completely useless to us. |
We found a solution for us. |
Same issue here despite having native-get-random-values package. |
Manually installing Here's what gets logged when I start the app and
Then when my app hits an uncaught exception, I see these warnings:
I'm still not seeing stack traces in Sentry. |
Same here using Expo SDK 45 |
Not sure if this will help other people, but when I switched from Expo Go to using expo-dev-client these warnings went away for me. Not saying that that's the right fix though. I still think there's an issue here though – I don't think people should have to use Also, the reason I wasn't getting stack traces was actually because I wasn't wrapping my error objects in an I had to change my code from this: Sentry.Native.captureException(error); to this: Sentry.Native.captureException(new Error(error)); |
Same issue here with:
Any ideas aside from switch from Expo Go to |
Same here
I've tried with and without |
Hello, same here. Started unexpactably |
Any update on this? |
Same |
My team and I are experiencing the same issues. Here is our stack trace with the following versions:
|
From the reports above, this seems to happen when using an incompatible version of Closing this as I cannot reproduce this on a new project. |
I am still seeing this issue using
Maybe I need to downgrade |
I too am receiving these errors:
Could this be related to my config setup? |
I also have this issue although I use |
Also still seeing with updated packages - no sentry event is being triggered:
|
If you have a reproducible example, then please open a new issue, and provide the requested information. If I initialize a new project with the correct versions (expo@46, [email protected], @sentry/[email protected]) then it works for me. If it doesn't work for you, we'll need a reproducible example. Commenting on a closed ticket does not help. |
https://github.com/CursedMun/Expo-Test - versions you mentioned still don't work |
are you running in Expo Go @CursedMun? If so - sentry-expo will be disabled regardless |
@kbrandwijk I've opened a new ticket with a repro Snack here: #285. Even with this very basic configuration I can confirm that Expo 46 and the latest sentry-expo version are not writing to Sentry, and are showing the warning discussed in this ticket. Thanks in advance for any help! |
Experiencing the same issue as many others above on Expo SDK 46. I don't know why this ticket was closed. |
Also experiencing the same issue: "sentry-expo": "~5.0.0", |
@BatDroid's solution worked for me as well. Expo 46 and Sentry 4.2.0 doesn't throw the warning and errors are properly received by Sentry. |
It also worked for me. Expo 46 and sentry-expo 4.2.0. |
I had the exact same errors when running Sentry in the |
What was the final solution? |
Still getting this issue, even with:
To add to that, I see these warnings when developing app on expo go:
as well as
|
For now i have to stick to version 4. Seems to be the last one that worked. |
any update on this..am facing this issue now
|
I am also facing this issue and have tried multiple versions of each package. Currently on this
|
I use
|
@stesvis I tried those versions and they didn't work. |
I'm on and it does not work.
I get the same error everyone else does.
So I downgraded to:
And I get this warning at startup.
And it still doesn't work of course.
|
Still facing the same issue |
Same here. This issue is closed. Is there any hopes of getting this forward? |
This fixed my problem and my first Sentry issues have been logged :-D |
Still facing the same issue |
This didn't work for me. I am starting to feel like Sentry abandoned Expo support... |
Bummer to see this. Glad I noticed it at the beginning of my project though so I can try out a different tool! |
It started working again, but you have to upgrade to Expo 49 and get the right version of sentry-expo, i believe v7.0 |
Still facing the same issue in Expo 50 when debug: true. |
Same. Any resolution to this ? |
2 years later and this issue is still occurring. |
This package is deprecated and Expo 50 now uses native sentry package so it will stay like this probably. Best to migrate when updating Expo to v50+. But currently there are still some issues. |
We are on expo 50 and did follow the official docs for sentry with expo. We still have this issue. Is there different documentation to use because it says right in it for sdk 50, for which steps we followed. |
https://docs.sentry.io/platforms/react-native/manual-setup/expo/ Mainly note the experimental notice in Sentry docs 😀 |
Sure, but you're pointing out that this is deprecated, and the new, supported version doesn't work but its okay because its marked "experimental"... what are folks supposed to do? Is there a different approach to using sentry for RN in expo? |
I guess we are in the process of transition. Old library still works and new one is experimental. I assume the work moved to new one because it makes sense and this one is no longer maintained. It probably does not make sense to expect any bug fixes and new features here. This is my opinion. I am not connected to expo nor sentry in any way but it makes sense imho. |
fixed? Sentry.init({
dsn: 'YOUR DSN HERE',
debug: true, // If `true`, Sentry will try to print out useful debugging information if something goes wrong with sending the event. Set it to `false` in production
integrations: [
new Sentry.ReactNativeTracing({
// Pass instrumentation to be used as `routingInstrumentation`
routingInstrumentation,
// ...
}),
],
}); where is should be: Sentry.init({
dsn: 'YOUR DSN HERE',
debug: true, // If `true`, Sentry will try to print out useful debugging information if something goes wrong with sending the event. Set it to `false` in production
integrations: [
new Sentry.ReactNativeTracing({
// Pass instrumentation to be used as `routingInstrumentation`
routingInstrumentation,
enableNativeFramesTracking: Constants.appOwnership !== 'expo', // Only in native builds, not in Expo Go.
// ...
}),
],
}); 1 line change and the error is gone for me. I made a PR to update the docs |
Our error got fixed after creating a new development build. As you can see Sentry does need a new build for native modules to be bundled up.
|
Summary
The package sentry-expo is causing the SentryError written in the title above. I have tried uninstalling and reinstalling various packages, as well as the backlog of fixes in the closed issues tab of this repo.
I was able to reproduce the issue with a clean build of an expo project (linked below) also running expo 44.0 SDK and the latest version of sentry-expo. Has anyone else encountered this problem recently?
Managed or bare workflow? If you have
ios/
orandroid/
directories in your project, the answer is bare!managed
What platform(s) does this occur on?
Android, iOS, Web
SDK Version (managed workflow only)
44.0
Environment
Expo CLI 5.0.3 environment info:
System:
OS: macOS 11.6.3
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
npm: 8.1.2 - ~/.nvm/versions/node/v16.13.1/bin/npm
Watchman: 2021.08.23.00 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3
Android SDK:
API Levels: 29, 30, 31
Build Tools: 28.0.3, 29.0.0, 31.0.0
System Images: android-30 | Google APIs Intel x86 Atom
IDEs:
Android Studio: 4.2 AI-202.7660.26.42.7486908
Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild
npmPackages:
expo: ~44.0.0 => 44.0.6
react: 17.0.1 => 17.0.1
react-dom: 17.0.1 => 17.0.1
react-native: 0.64.3 => 0.64.3
react-native-web: 0.17.1 => 0.17.1
npmGlobalPackages:
expo-cli: 5.0.3
Expo Workflow: managed
Reproducible demo or steps to reproduce from a blank project
Here is a demo repository where I am encountering the same issue as on the app I am developing: https://github.com/tigar/sentry-test
The text was updated successfully, but these errors were encountered: