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

Add new captureFeedback to RN SDK #3859

Open
dalnoki opened this issue Jun 5, 2024 · 3 comments
Open

Add new captureFeedback to RN SDK #3859

dalnoki opened this issue Jun 5, 2024 · 3 comments

Comments

@dalnoki
Copy link

dalnoki commented Jun 5, 2024

Description

This function is the base functionality needed to allow capturing user feedback while including tags, replay_id, trace_id, etc.
It's part of the 'new user feedback' product (getsentry/sentry#64671) that was shipped for Web. That included a built-in widget, that allows screenshot attachment, and under the hood relies on this new function that deprecates the old captureUserFeedback which required an event_id. The new function optionally takes a related event_id and will contain relevant context stand alone.

Since RN is built on top of the JS SDK we might be able to re-export the function. But we need to verify that connection to tracing and replays will work properly. See:

This means a new envelope format for feedback was introduced.
The new Feedback product architecture has thoroughly documented by @aliu39 here:

This new function will allow outgoing feedbacks to be tied to Session Replay, which is currently Open Beta and we're working on GA:

The develop docs have not been added yet, but the ticket with details about it is here:

Relates to:

@bruno-garcia
Copy link
Member

@krystofwoldrich
Copy link
Member

The API without UI, will be available in RN SDK v6 (the next major) which includes JS v8 which includeds the new captureFeedback API.

@krystofwoldrich
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Status: Backlog
Development

No branches or pull requests

3 participants