[PLAT-4706] Fix thread sending behaviour #1077
Merged
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.
Goal
To stop
threads
being sent if the notifier has been configured not to via thesendThreads
property.Prior to this change,
threads
would contain a single object.Changeset
-[BugsnagClient notify:]
has been amended to send an emptythreads
array if threads should not be sent.-[BugnagEvent initWithKSCrashData:]
has been amended to send an emptythreads
array if a single thread was captured - this is what KSCrash does when if thread sending is disabled (so that the offending stacktrace is captured.)Testing
Verified through E2E tests, and manually tested using example app.