You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
User feedback is not captured with versions older than 3.2.0 #2180
var eventId = SentrySdk.CaptureMessage("An event that will receive user feedback.");
SentrySdk.CaptureUserFeedback(eventId, "user@example.com", "It broke.", "The User");
Could you share a repro? Not sure what could be going wrong there
I attached it to my original message with the bug report,
Oh, my bad.
I can reproduce this now but doesn't seem to be related to the version.
It seems like we expect the email to be a valid email (at least have a @ and . in my tests).
And the order of the arguments here are important. Where you have $"{header} | {_inputField.text}" is actually the email field on the old API. And where you have "email", it's the comments.
// Doesn't work
// SentrySdk.CaptureUserFeedback(eventId, $"header | _inputField.text", "email", userName);
// But this works
SentrySdk.CaptureUserFeedback(eventId, "user@example.com", $"header | _inputField.text", userName);
Okay, I see. Thanks for helping me with figuring it out!
In the new API it's message - email. In the old one it's email - message.
I was researching the 3.2.2 crash, and had to switch versions back and forth.
Would be nice to see an error, like "wrong email format"
yeah we changed the order of the args then and didn't realize this is easy to mix up. A debug message makes sense. cc @jamescrosswell might be a quick win (!contains(@) just a best effort thing
Activity
bruno-garcia commentedon May 30, 2025
does sentry show the error but no feedback linked?
there's also no feedback if you in the feedback page itself?
could you share your org slug so I can check the stats for dropped data?
cc @jamescrosswell @Flash0ver could the addition of the new api have broken the old?
pdyatlov commentedon May 30, 2025
No error. The event goes out just fine, but does not appear on my Sentry dashboard
Sending feedback from 3.2.0 and the new API works. When I rollback to 3.1.0 and use CaptureUserFeedback from the same spot in code, it stops working
white-ink, 4507232060243968
bruno-garcia commentedon May 30, 2025
That's odd, looking at:
There were no changes to
CaptureUserFeedbackand the tests are still there and passing. I'll test it out locally.bruno-garcia commentedon May 30, 2025
Tested with a CLI on .NET and it worked:
Could you share a repro? Not sure what could be going wrong there
pdyatlov commentedon May 30, 2025
I just double and triple checked with both a build and editor.
3.1.0, after a feedback is sent (SendUserFeedback)
3.2.0, after a feedback is sent (obsolete SendUserFeedback)
3.2.0, after a feedback is sent (SendFeedback)
Anonymous - Steam logged off
Paul Dy - Steam logged in
That's what I call when the game starts, maybe that affects it somehow?
11 remaining items
pdyatlov commentedon May 30, 2025
I attached it to my original message with the bug report,
bruno-garcia commentedon May 30, 2025
Oh, my bad.
I can reproduce this now but doesn't seem to be related to the version.
It seems like we expect the email to be a valid email (at least have a
@and.in my tests).And the order of the arguments here are important. Where you have
$"{header} | {_inputField.text}"is actually the email field on the old API. And where you have"email", it's thecomments.Doesn't matter the version on my tests.
pdyatlov commentedon May 30, 2025
Okay, I see. Thanks for helping me with figuring it out!
In the new API it's message - email. In the old one it's email - message.
I was researching the 3.2.2 crash, and had to switch versions back and forth.
Would be nice to see an error, like "wrong email format"
bruno-garcia commentedon May 30, 2025
yeah we changed the order of the args then and didn't realize this is easy to mix up. A debug message makes sense. cc @jamescrosswell might be a quick win
(!contains(@)just a best effort thingbruno-garcia commentedon Jul 17, 2025
Some updates, we replaced the email validation, so feedback with invalid email wont' be dropped anymore