-
-
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
Cannot set issue title for messages or errors #1033
Comments
Hmm, which method are you using to capture the messages/errors? |
No problem. I looked at our code and Sentry logs again and the issue is not with the captureMessage, it is just within the captureException. We recently upgraded* from
The odd thing is the |
Ah, so |
Closing this on the basis of being more than a year old with no updates. If the issue still persists, feel free to reopen. |
@carlosen14 if you find any solution please post here |
its work, thanks @matheuscouto |
OS:
Platform:
SDK:
@sentry/react-native
(>= 1.0.0)react-native-sentry
(<= 0.43.2)SDK version: 1.4.5
react-native
version: 0.60.6Are 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:
N/A this is a configuration issue. All issue titles are '' and I cannot for the life of me figure out how to manually set them.
Configuration:
(
@sentry/react-native
)or
(
react-native-sentry
)I have following issue:
When error or messages are captured to Sentry the title is set to '' this is a regressing from our previous version. I have read through the docs and I cannot find mention of a title property anywhere, however I did find it within the JSON of a reported issue with this title.
Here is an example:
Maybe I missed it in the documentation somewhere? Any and all help is greatly appreciated. Thanks!
Steps to reproduce:
Actual result:
Attached is a screenshot of the behavior.
Expected result:
The ability to set titles, so the Sentry logs are easily readable.
The text was updated successfully, but these errors were encountered: