-
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
Promise rejection: SentryError: Native is disabled #218
Comments
I'm using Expo Go, not EAS, and running into this whenever I try to use |
@cruzach the error message in this issue is different than in #216: |
I have the same issue on Android ( |
Is it possible that this issue is reopen? I am experiencing the same issue with a brand new expo app. I am running my app on a simulator (iphone 8) with expo start. I noticed that the Issue is created on Sentry regardless
I added Sentry.init in App.json
Modified app.json
And when I try to launch an exception like this
|
The same thing is happening in our project, it is most likely this issue still happening. |
I don't think this is the same as the original issue in this ticket, since the stacktrace is different, but we're seeing this as well. |
@geraldosalazar16 @MorenoMdz please see #243 , is this more similar to what we're seeing? |
Yes, this is happening for us with a very new almost empty expo project on v44. It happens whether or not we use Logs:
|
In our case it happens even when passing in However, it appears that the reports still come through to Sentry. So I suppose we just have to ignore the reams of error messages this generates, until someone gets around to investigating it? |
hi there! is there a particular reason why folks want to enable sentry in development? the idea behind the it is expected to see something like "Sentry Logger [Warn]:, [SentryError: Native is disabled]" in Expo Go because the native sentry SDK is not installed there. here's an example of a config where you do not receive such a warning in Expo Go:
feel free to toggle |
Makes sense, I think in our case it was a new app (iirc) and I just wanted to see if the Sentry integration was working, certainly didn't expect reams of random errors.
|
we have a QA team test in various environments, most of which are not production. Sometimes it's very helpful to enable Sentry in those environments in order to collect data. Since Sentry filters based on environment, it's not an issue in any manner. Why would we not? |
In my case I see: " WARN Sentry Logger [warn]: Event was skipped as native SDK is not enabled." So contrary to what @brentvatne suggested, it seems I can't currently test the backend integration from Expo Go. Nothing has shown up in Sentry.io so I'm not sure it's going to correctly connect when in production. |
Summary
Trying to get Sentry's performance/tracing enabled on web & mobile.
The tracing works on web builds, but not yet on for mobile and there are promise rejections.
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?
iOS
SDK Version (managed workflow only)
41
Environment
Reproducible demo or steps to reproduce from a blank project
I'll work on a demo. I'm new to the frameworks.
Here's a code mashup of Sentry.init()
The text was updated successfully, but these errors were encountered: