-
-
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
No errors reported #6
Comments
Can you please add
|
A clue!
|
Did you make sure you copied the DSN from the documentation? https://docs.sentry.io/clients/react-native/#client-configuration Looks like you are missing the secret part. |
Ah, it wasn't clear that the DSN format changed. The Seems to have fixed that error, but still not seeing errors reported. Using
Using
Using |
Hello guys, I'm currently doing the same as @nicinabox , and having the same result so far. Only EDIT: I tested with an iOS app built in production settings through Hockey App, and a |
Please make sure you also added the code to you https://docs.sentry.io/clients/react-native/#client-configuration Also note that |
I did add the code in the But it does not anyhow send the crashes in my simulator... However it works on my production apps. |
+1 |
Can you guys please send me your sentry url via email at [email protected] |
I am not seeing any issues reporting when my development build iOS app crashes. Can you confirm that this is because it ignores them by default for development builds and only reports them for release builds? If that isn't the case, I might be getting this bug too. |
Nothing being reported on iOS here |
Can you guys please add a bit more context ... It should definitely report something in DEBUG so it should work. |
@matt-oakes Can you try sending a normal message like this:
It depends on the error if it will be sent, it will definitely be sent in release, in DEBUG not every error will be sent e.g.: if you see a redbox the error will not be sent. |
@HazAT I think the issue I'm seeing is unrelated then. I think it's just because it's running in debug mode and is showing a red box. Maybe the documentation just needs to be a little clearer on this. Thanks for the help! |
Hey, please upgrade to the latest release 0.11.0. |
@HazAT We are also not getting any errors reported but only in release mode. Works fine in Debug. Latest version as of now. Please reopen this issue. |
@alizain-wal Hey, I've just tested it with a release build, it seems to work fine.
|
@HazAT Thank you for your response. Verbose log:
|
Here is my code for index.ios.js
This is working in IOS simulator but it's not working in test app that I archived and deployed for testing purposes. However, sending messages to sentry is working on both: Sentry.captureMessage('This is test message from Sentry IOS SDK!'); Where can I find log in order to check what is wrong if my app is running on an actual device? Thanks in advance. Nikola |
Hey @Nik0licA @alizain-wal |
@Nik0licA @alizain-wal |
Tried both versions with no success for the device :(. |
|
@HazAT I suppose that you are refering to me. |
@Nik0licA Yes sry, I meant you. |
@HazAT Hi, I tried it with a new version, removed node_modules, in xcode->project->clean, installed sentry via npm with a rest of modules, unlink/link sentry (sentry.properties are created earlier) and it worked for the first time I tried, both, simulator and device builds. However, as we have two "branches" on sentry.io, one for dev and other for production crash reporting etc..I wanted to switch from production to a dev branch (by branch I mean my-company/my-awesome-project-dev-branch) also I reinstall everything, unlink/link sentry and now both branches are not working for device builds. Messages from sentry are working in any case. You can see here, the first in a log is message (Sentry.captureMessage()) and other is intentional error made by me in order to test sentry. It is from the IOS simulator. |
@HazAT One more question related to this. Do I need to go through whole deleting node_modules, reinstalling sentry etc. process if I want to change from dev to production or I just need to comment and uncomment related lines like I did here in these files?: Token stays the same as token is used to authorize SDK with sentry.io no matter what project I am running, right? Thanks in advance for support! :) |
@HazAT For Android builds sentry is working great every time, in emulator and the device. |
@HazAT hello, thank you for the effort and work on this library. I have a similar issue as the guys above:
import { Sentry, SentryLog } from 'react-native-sentry';
Sentry.config('https://aaa:[email protected]/ccc', {
logLevel: SentryLog.Verbose,
}).install(); Best regards! |
@samuelchvez Is it only on Android? ...
import io.sentry.RNSentryPackage;
...
public class MainApplication extends Application implements ReactApplication {
....
@Override
protected List<ReactPackage> getPackages() {
return Arrays.<ReactPackage>asList(
new MainReactPackage(),
new RNSentryPackage(MainApplication.this)
);
}
... |
@HazAT yes, it looks exactly like that. I have not tested it on iOS. Thanks for your help |
"react-native": "0.51.0", Working on troubleshooting this. iOS crashes don't seem to be getting reported. When I test
reports the message and the crash. |
@HazAT please add full manual instruction for iOS & Android it will be useful ;) |
For everyone who has the same issue that on Android crashes/JS errors war not reported: It works when I disable the native integration for Android
|
Is there reason why android's native integration doesn't work and when this will be fixed? |
@HazAT react-native-sentry 0.39 My config:
|
@antonsivogrivov set disableNativeIntegration:true for every platform fixed my issue. @jjoe64 Can you explain why disableNativeIntegration:true is working? What is the cons of setting disableNativeIntegration:true. |
Has this been resolved? I can't send any logs except for Sentry.captureMesage() I'm using: |
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);
}); |
ErrorUtils.setGlobalHandler can capture "throw new RuntimeException("Error");" from android ? |
@EduTel This issue is very old if you are experiencing any problems feel free to create a new issue here in the repository. |
We're using an on premise install (8.14.1) and I'm trying to setup
react-native-sentry
I've configured according to the docs and everything seems to build and run fine, but no errors actually show up. I'm testing from the Simulator and manually throwing an error from the root component on mount.The text was updated successfully, but these errors were encountered: