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
Sentry has a User Feedback feature that is able to show the feedback collected from a user following an error, or simply initiated by a user (without the need to be connected to an error/event).
The feedback collection allows attaching trace information as well as Session Replay. In addition to other context like tags.
In terms of SDK support, in JS we added a web widget, that's easy to add to the screen:
The goal is to add a similar capability to mobile SDKs.
This SDK already has a function called CaptureUserFeedback which requires an event_id to work. This is the 'original' support for feedback that required an event to tie the feedback to. It didn't allow attachments, or tags as those would go on the error anyway.
The new protocol allows for the feedback itself to be self contained.
The SDKs have a new method that represnets this new protocol: CaptureFeedback. The old one should be deprecated in favor of the new one
But there are all kinds of ways people could be building their UI in .NET (Blazor, ASP.NET Core MVC, AJAX, SPA front ends, native Android/iOS UI, WinForms, UWP, WinUI, WPF, MAUI etc.).
Maybe we just contain the scope of this issue to building Widgets for MAUI and ASP.NET Core? Even those two, I think, will keep us busy with people requesting ways to style them and customise them etc.
Sentry has a User Feedback feature that is able to show the feedback collected from a user following an error, or simply initiated by a user (without the need to be connected to an error/event).
The feedback collection allows attaching trace information as well as Session Replay. In addition to other context like tags.
In terms of SDK support, in JS we added a web widget, that's easy to add to the screen:
The goal is to add a similar capability to mobile SDKs.
This SDK already has a function called
CaptureUserFeedback
which requires anevent_id
to work. This is the 'original' support for feedback that required an event to tie the feedback to. It didn't allow attachments, or tags as those would go on the error anyway.The new protocol allows for the feedback itself to be self contained.
The SDKs have a new method that represnets this new protocol:
CaptureFeedback
. The old one should be deprecated in favor of the new oneSee:
captureFeedback
function sentry-cocoa#4187The widget has been added to the iOS SDK with quite a few features already. And is also being added to the other major SDKs:
Some ideas are new and are not aligned across all SDKs, for example:
But ideally we have a similar behavior/look/feel as much as that makes sense. Things should be idiomatic (e.g: swiping down in the modal removes the feedback widget for example)
The text was updated successfully, but these errors were encountered: