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
Commit 31d6ad3
Browse filesBrowse the repository at this point in the historyBrowse files
feat(feedback)!: always reject sendFeedback with an Error
Previously, sendFeedback's async rejection paths (timeout, 403, generic
transport error) rejected with a plain string, while the sync-throw paths
(empty message, no client) threw an Error. Unify on Error for all paths so
consumers can rely on a consistent rejection shape.
BREAKING CHANGE: sendFeedback now rejects with an Error instead of a string.
The message text is unchanged and is still customizable via the
`errorMessages` hint, so consumers reading it should switch from the
rejection value itself to `error.message`.
Copy file name to clipboardExpand all lines: MIGRATION.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -520,6 +520,22 @@ Two consequences to be aware of when upgrading:
520
520
-**Issue grouping:** Grouping in Sentry differs for events with and without stack traces, so you may see new issue groups after upgrading.
521
521
-**Release health:** Events with a stack trace are counted as errors, so a `captureMessage` call (including messages emitted by `captureConsoleIntegration`) now marks the current session as _errored_. This affects errored-session counts but does **not** mark sessions as crashed, so crash-free session rate is unaffected. If you use `captureMessage` for purely informational output, consider using Sentry Logs instead, which is better suited and does not affect release health.
522
522
523
+
### `sendFeedback` rejects with an `Error`
524
+
525
+
Affected SDKs: All SDKs running in the browser.
526
+
527
+
`Sentry.sendFeedback()` now rejects with an `Error` in all cases. Previously it rejected with a plain string when the request timed out, was rejected with a 403, or otherwise failed to send, while the synchronous validation paths (empty message, no client configured) already threw an `Error`. The message text itself is unchanged, and is still customizable through the `errorMessages` hint, so read it off `error.message`:
528
+
529
+
```js
530
+
try {
531
+
awaitSentry.sendFeedback({ message:'Hello' });
532
+
} catch (error) {
533
+
// v10: a string on send failures, an Error on validation failures
0 commit comments