fix: CaptureFeedback now supports multiple attachments correctly#5077
fix: CaptureFeedback now supports multiple attachments correctly#5077jamescrosswell merged 3 commits intomainfrom
CaptureFeedback now supports multiple attachments correctly#5077Conversation
Semver Impact of This PR⚪ None (no version bump detected) 📋 Changelog PreviewThis is how your changes will appear in the changelog. Breaking Changes 🛠
Features ✨
Fixes 🐛
Dependencies ⬆️Deps
Other
🤖 This preview updates automatically when you update the PR. |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #5077 +/- ##
==========================================
- Coverage 74.00% 74.00% -0.01%
==========================================
Files 499 499
Lines 18066 18067 +1
Branches 3518 3519 +1
==========================================
Hits 13370 13370
- Misses 3837 3838 +1
Partials 859 859 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
It was just copied from the JS SDK which does have this restriction, but that's just a browser/JS thing, not a protocol thing so we should remove. |
|
Yeah I think when I first implemented it the protocol wouldn't accept more than one Attachment. We did discuss that and the server was changed - we just never circled back to address the SDK. Thanks @bitsandfoxes ! |
CaptureFeedbackCaptureFeedback now supports multiple attachments correctly
Updated [Sentry.AspNetCore](https://github.com/getsentry/sentry-dotnet) from 6.3.0 to 6.3.1. <details> <summary>Release notes</summary> _Sourced from [Sentry.AspNetCore's releases](https://github.com/getsentry/sentry-dotnet/releases)._ ## 6.3.1 ### Fixes 🐛 - fix: Workaround FileNotFoundException on Android when recovering sessions by @jamescrosswell in [#5084](getsentry/sentry-dotnet#5084) - fix: `CaptureFeedback` now supports multiple attachments correctly by @bitsandfoxes in [#5077](getsentry/sentry-dotnet#5077) ### Dependencies ⬆️ #### Deps - chore(deps): update Native SDK to v0.13.5 by @github-actions in [#5119](getsentry/sentry-dotnet#5119) - chore(deps): update CLI to v3.3.5 by @github-actions in [#5093](getsentry/sentry-dotnet#5093) - chore(deps): update Native SDK to v0.13.4 by @github-actions in [#5081](getsentry/sentry-dotnet#5081) - chore(deps): update Java SDK to v8.37.1 by @github-actions in [#5071](getsentry/sentry-dotnet#5071) - chore(deps): update CLI to v3.3.4 by @github-actions in [#5068](getsentry/sentry-dotnet#5068) - chore(deps): update Java SDK to v8.37.0 by @github-actions in [#5069](getsentry/sentry-dotnet#5069) - chore(deps): update Cocoa SDK to v9.8.0 by @github-actions in [#5044](getsentry/sentry-dotnet#5044) - chore(deps): update Java SDK to v8.36.0 by @github-actions in [#5036](getsentry/sentry-dotnet#5036) - chore(deps): update epitaph to 0.1.1 by @github-actions in [#5036](getsentry/sentry-dotnet#5036) ### Other - chore: Update validate-pr workflow by @stephanie-anderson in [#5108](getsentry/sentry-dotnet#5108) - ci: fix workflows that always fail for fork PRs by @jamescrosswell in [#5065](getsentry/sentry-dotnet#5065) Commits viewable in [compare view](getsentry/sentry-dotnet@6.3.0...6.3.1). </details> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>
Follow up on: #3981
I could not find any source, neither in the dev docs nor on Sentry, for the "only one attachment per feeedback" restriction. The envelop created from a feedback can hold as many attachments as any other and will get processed by Sentry accordingly.