Skip to content
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

SentryUser.name & .segment properties ignored #3933

Closed
lhunath opened this issue May 2, 2024 · 7 comments
Closed

SentryUser.name & .segment properties ignored #3933

lhunath opened this issue May 2, 2024 · 7 comments

Comments

@lhunath
Copy link
Contributor

lhunath commented May 2, 2024

Platform

iOS

Environment

Production, Develop

Installed

Swift Package Manager

Version

8.25.0

Did it work on previous versions?

No response

Steps to Reproduce

  1. Create a SentryUser with a certain identifier.
  2. Set the user's username and name properties.
  3. Report a Sentry event.
self.sentryUser = userId.flatMap(Sentry.User.init)
self.sentryUser?.email = userEmail
self.sentryUser?.username = userName
self.sentryUser?.name = userName
self.sentryUser?.segment = userManager == "yes" ? "manager" : "user"
SentrySDK.setUser(self.sentryUser)

Example event: us.sentry.io.json

Expected Result

The event payload & web app reports the user's human readable name and segment.

Actual Result

The event payload & web app only report the user's userId, email and userName.
image

Are you willing to submit a PR?

No response

@lhunath lhunath changed the title SentryUser.name property ignored SentryUser.name & .segment properties ignored May 2, 2024
@brustolin
Copy link
Contributor

brustolin commented May 3, 2024

Hello @lhunath, thanks for reaching out.

I could reproduce this, but it seems that the behaviour is not straight forward. After waiting a little bit more and refreshing the issue page the name appears.

Can you test this?

@lhunath
Copy link
Contributor Author

lhunath commented May 3, 2024

I have not seen the missing information appear on the issue page (this is the issue page for the error event attached in the description). I should point out that the information is also missing from the event JSON, so it would be surprising to me if it did show up later.

@brustolin
Copy link
Contributor

I cant reproduce this. The name appears, but sometimes I need to refresh the issue page to see it.

@getsantry
Copy link

getsantry bot commented Jun 13, 2024

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community, I will leave it alone ... forever!


"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

@lhunath
Copy link
Contributor Author

lhunath commented Jun 13, 2024

Segment continues to be absent from the issue page.
sentry.json
image

@kahest
Copy link
Member

kahest commented Jun 17, 2024

user.segment is going to be removed from the product side and isn't supported by the new Contexts view. We're going to deprecate and remove the property from all SDKs soon. Apologies for the confusion.
If you need to report segment information, you can use Context or Tags.

@getsantry
Copy link

getsantry bot commented Jul 10, 2024

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community, I will leave it alone ... forever!


"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

@kahest kahest closed this as not planned Won't fix, can't repro, duplicate, stale Jul 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Archived in project
Archived in project
Development

No branches or pull requests

4 participants