-
-
Notifications
You must be signed in to change notification settings - Fork 338
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
Does not report crashes #447
Comments
Confirm, the same situation. Installed the latest release (0.38.3). Crashes don't send but custom captured messages are shown in the log. |
I just tried it and it works.
|
Thanks for reply! I’ve been trying on iOS, any suggestions what can go
wrong with the configuration for it?
…On July 30, 2018 at 12:54:23 AM, Daniel Griesser ***@***.***) wrote:
I just tried it and it works.
Please make sure your MainApplication.java looks something like this:
...
import io.sentry.RNSentryPackage;
...
public class MainApplication extends Application implements ReactApplication {
...
@OverRide
protected List<ReactPackage> getPackages() {
return Arrays.<ReactPackage>asList(
new MainReactPackage(), new RNSentryPackage()
);
}
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#447 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AG8TmsRErkSUQa-0fafhwxqgOjR0YqCzks5uLruvgaJpZM4Vfdyk>
.
|
@HazAT Mine looks exactly the same, even built-in native crash method doesn't trigger error event in the dashboard (crashes the app though) |
@vovanmix @sergeylaptev did you ever figure this out? We don't see any crashes in Segment, though JS exceptions and messages work fine. |
Any news about this? I am trying Sentry on both ios and android it triggers only when using |
Getting reports from customers of the app crashing and we see nothing on our end. |
+1 |
same issue here... |
Same here |
+1 |
Same here. As workaround I override the global error handler to include the Sentry log. // Error handler setup
let originalHandler = ErrorUtils.getGlobalHandler();
ErrorUtils.setGlobalHandler((error, isFatal) => {
Sentry.captureException(error);
originalHandler(error, isFatal);
}); |
@prof18, not working for me. react-native: 0.57.8, react-native-sentry: 0.43.2 EDIT: sorry, my bad, I tested with the debug build where Sentry was disabled. It does work. Thank you! |
I am closing all old issues, please if this is still a problem feel free to revive it. |
OS:
Platform:
Output of
node -v && npm -v && npm ls --prod --depth=0
Config:
I have following issue:
Native crashes are not reported. I have a detached expo app, I'm using
react-native-sentry
instead ofsentry-expo
because it's detached, I didreact-native link react-native-sentry
. Running the app from expo.When the app crashes on iOS, or when I do
Sentry.nativeCrash();
in the simulator, nothing gets reported.Sentry.captureMessage('TEST message');
reports correctly.It also wan't reporting crashes before I detached expo, with
sentry-expo
.The text was updated successfully, but these errors were encountered: