-
-
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
No JS-level errors sent in Release mode #700
Comments
Does using a older version fix this? |
Is there any particular version I should try going back to? As I say, this hasn't worked for a while so not sure how far to go back |
I have the same problem ! :( |
Still reproducible on RN 0.61.5 + Sentry 1.1.0 |
Any update on this? Facing same issue on |
It's dumb this is open for so long when there are paying customers affected by this |
I managed to fix this after speaking to tech support. Achieved this by switching from
For some reason, ignoreErrors was blocking anything |
I am closing this since it seems to be solved. |
Are you suggesting essentially not to use "ignoreErrors" and do basically do the ignoring in beforeSend, seems kind of hacky...but is what it is I guess... |
@Aryk Can I see what you have set for |
Sure ...here's the entire code: Sentry.init({
dsn: <hidden>,
enableInExpoDevelopment: true,
debug: true,
environment: Constants.manifest.releaseChannel || "development",
attachStacktrace: true,
ignoreErrors: [
"GraphQL Error (Code: 502)", // On development, get this weird intermittent message.
"Background Location has not been configured. To enable it",
"Network request failed",
"Rendered fewer hooks than expected. This may be caused by",
],
});
// Keys are snake_case because this was the convention in the documentation.
Sentry.setTags({
device_name: Constants.deviceName,
ios_model: Constants.platform.ios?.model,
ios_build_number: Constants.manifest.ios?.buildNumber,
android_version_code: Constants.manifest.android?.versionCode,
revision_id: Constants.manifest.revisionId,
release_id: Constants.manifest.releaseId,
version: Constants.manifest.version,
// system_version: Constants.systemVersion.toString(),
}); |
@Aryk So is the event being dropped an event that shouldn't be dropped I assume right? And can I see you have already set |
Sure...how do I get you the logs? I don't see it write to any log files in my directory. I can give you the console output, does that work? |
@Aryk Hmm that looks correct, I see you have |
Wow ok...I will turn debug off then. lol Thanks for pointing that out...this error was driving me crazy |
OS:
Platform:
SDK:
@sentry/react-native
react-native-sentry
react-native
version: 0.60.6Init Code:
I have following issue:
Our React Native sentry installation no longer reports JS-level bugs. I'm now on react-native 0.60.6 & @sentry/react-native 1.0.9. I'm currrently testing on iOS but it hasn't been working on Android either. It hasn't been working for us for a while so don't think it's a new version issue.
I've tried removing and reinstalling the library.
When I run in dev mode, any error I throw appears in Sentry. But if I take the same code and run in release mode nothing gets sent. I can see the following in the logs in Xcode:
Steps to reproduce:
throw new Error('test')
on rootApp.js
Actual result:
Expected result:
The text was updated successfully, but these errors were encountered: