-
-
Notifications
You must be signed in to change notification settings - Fork 343
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
Custom setExtra and setTag values are not showing in version: 1.3.7 #826
Comments
I have a similar Issue. In my case, i set two tags, but in the dashboard only shows one. |
@jennmueng are you aware of this? trying to reproduce this would be the first step. |
I found something which might be related to this. I was setting tags using a dictionary back in 1.3.4 using setTag() and it is working fine. However, in 1.7.2 the function is changed and it is expecting only strings and introduced a new function called setTags(). Maybe I missed that out in upgrade guide but I cannot really find it. So, would be nice if we can add it in the guides here 🙂 https://docs.sentry.io/platforms/javascript/enriching-error-data/additional-data/adding-tags/ Thanks! |
@marandaneto happy to send a PR 🙂 if it will be helpful. |
@Aung-Myint-Thein that's true. I think that change doesn't reflect on all the other SDKs that depend on sentry-javascript, yet. What's about adding to the README? there's a |
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. for the docs issue: getsentry/sentry-docs#4275 |
OS:
Platform:
SDK:
@sentry/react-native
react-native-sentry
SDK version: 1.3.7
react-native
version: 0.60.5Are you using Expo?
Are you using sentry.io or on-premise?
Configuration:
I have following issue:
Sentry.setExtra
andSentry.setTag
values are not showing in sentry issue dashboardAlso checked using
beforeSend
Custom extras and tags are not showing, only
Steps to reproduce:
1.3.7
Actual result:
Expected result:
The text was updated successfully, but these errors were encountered: