Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Despite the newer features designed to limit report sizes, reports can still occasionally exceed the limit, resulting in them being silently deleted without being sent. When this happens frequently, there’s no way to detect it, which can lead to ticket prioritization problems and potential business losses.
This PR introduces a new callback,
onSendFailureBlock
, which is triggered when a report is dropped by the system without this being the intention of the sender.I understand that Bugsnag typically doesn’t accept new features via PRs, but this one is straightforward and could provide significant value to end users. I’d greatly appreciate it if you could consider merging it as is or making any necessary adjustments before merging.
Thank you!