-
-
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
Some beforeSend
event changes are ignored on Android
#2896
Comments
Hi, thank you for the details. This is caused by the way we currently enrich the contexts on Android. We send the event from JS to Android after the JS beforeSend and there we add the information. Some of the values can be removed by providing some placeholder value like This won't work for beforeSend: (event: Sentry.Event) => {
event.user = {
id: '<retracted>',
}
event.environment = '<retracted>'
event.contexts = event.contexts || {}
event.contexts.device = {
type: '<retracted>',
}
// This won't work as Android will add a new os object to the contexts
// event.contexts.os = event.contexts.os || {}
// event.contexts.os.version = '<retracted>'
// event.contexts.os.kernel_version = '<retracted>'
return event;
}, |
beforeSend
event changes are ignored on Android
Closing this as we track it in getsentry/team-mobile#11 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
OS:
Platform:
SDK:
@sentry/react-native
(>= 1.0.0)react-native-sentry
(<= 0.43.2)SDK version: 5.1.1
react-native
version: 0.70.5Are you using Expo?
Are you using sentry.io or on-premise?
If you are using sentry.io, please post a link to your issue so we can take a look:
[Link to issue]
Configuration:
(
@sentry/react-native
)I have following issue:
App running on Android ignores
delete
flags. That causes Sentry to log things I don't want (like device info) on Android. Works flawlessly on iOS.Steps to reproduce:
Actual result:
delete
is ignored on AndroidExpected result:
delete
should not be ignoredThe text was updated successfully, but these errors were encountered: