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 user feedback capability to the Native SDK #1

Closed
wants to merge 18 commits into from

Conversation

tustanivsky
Copy link
Owner

This PR introduces a new API allowing to create/capture user feedback for specific events (similar functionality is offered by native Android and Apple SDKs).

It will be later exposed to the Unreal Engine plugin where user feedback capabilities have been requested recently. While the existing user feedback endpoint provides an alternative it requires deviating from our current approach of utilizing the native SDKs for client app communication with Sentry there.

Related to getsentry#885

Copy link

github-actions bot commented Mar 14, 2024

Fails
🚫 Please consider adding a changelog entry for the next release.
Messages
📖 Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Instructions and example for changelog

Please add an entry to CHANGELOG.md to the "Unreleased" section. Make sure the entry includes this PR's number.

Example:

## Unreleased

- Add user feedback capability to the Native SDK ([#1](https://github.com/tustanivsky/sentry-native/pull/1))

If none of the above apply, you can opt out of this check by adding #skip-changelog to the PR description.

Generated by 🚫 dangerJS against 5c308e7

@tustanivsky tustanivsky changed the title Add user feedback Add user feedback capability to the Native SDK Mar 14, 2024
@bruno-garcia
Copy link

Hey @tustanivsky did you mean to create this PR on upstream getsentry/sentry-native?

@tustanivsky
Copy link
Owner Author

Hey @tustanivsky did you mean to create this PR on upstream getsentry/sentry-native?

Yeah, that was the plan! I'll polish things up and make a proper PR to the main repo once it's ready.

@tustanivsky
Copy link
Owner Author

tustanivsky commented Mar 19, 2024

Closing this now as another PR to the main repo has been created

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants