-
-
Notifications
You must be signed in to change notification settings - Fork 337
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
Issues not reported on Android - Error reading envelope #1104
Comments
@martinriviere Can I see the full Logcat errors, and also the JS console logs outputted by |
@jennmueng thanks for your reply!
The "Sentry error" (secont to last line) is the test error I throw in JS when pressing a button. Here is my JS console logs:
Thanks for your help! |
Is there any update on this? It is reproducible on the Pixel 4/a, Android 11 |
Yes I am also getting this, I have the same RN version and Sentry version as OP. Further down the log I also get an SSL error?
|
@jlmcdonnell It could be related to this issue with Pixel 4/4a on Android 11: getsentry/sentry-java#904 @martinriviere Are you also on Android 11 with Pixel 4/4a, it could be the issue above. @markgibaud |
@jennmueng I'm not, and I get the same issue on the simulator Nexus 5X running Android 9, and on my real device, Xiaomi Mi Mix 2S also running Android 9. |
I'm getting these crashes for all Pixels in prod trying to use my App. I'm not sure if the fixes here have been propagated in. I'm needing to filter out Pixel handsets for now and I'm going to attempt the work-arounds described in the |
@allenmanning Are you using version 2.0.0? The fixes should be included there. Let me know if this issue is fixed, so I can close this issue. |
Tested on 2.0.0 - still valid |
no update on this? still I can't send anything with v 2.2.1 |
Can you pass |
Hi and Thanks for your fast reply! |
@ph98 Hmm are you correctly initializing the Sentry SDK if no logs show? They should always show if the SDK is being correctly initialized. Make sure everything is correct following our documentation. |
I don't get any issues reported on Android too. Looks like a problem on Android 10 only, as on Android 8 it works for me. On Android 10 I get a SSL error using 2.6.0.
|
This or something similar seems to be fixed on 5.0.1. Was happening on 2.3.2 of native android sdk on OnePlus 7 Pro |
cc @marandaneto |
are you using sentry.io or on-premise? also, what's the version of your Java SDK? please run |
as naive as it seems but in my case it was my emulator wifi that was not connected! |
Closing the issue as a part of large repository cleanup, due to it being inactive and/or outdated. There's a large chance that this issue has been solved since. |
OS:
Platform:
SDK:
@sentry/react-native
(>= 1.0.0)react-native-sentry
(<= 0.43.2)SDK version: 1.8.2
react-native
version: 0.62.2Are you using Expo?
Are you using sentry.io or on-premise?
Configuration:
I have following issue:
Issues are reported on iOS, but I can't manage to make it work on Android on both debug and release builds.
Steps to reproduce:
Actual result:
Nothing is reported on Android while it works as expected on iOS. Sentry.nativeCrash() doesn't crash the app on Android while it does on iOS.
In AS, Logcat shows 'Error reading envelope' when I trigger the errors.
Expected result:
Issues should be reported on Android.
The text was updated successfully, but these errors were encountered: