Release v7.16.3 #1715
Merged
Release v7.16.3 #1715
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bump bugsnag-android dependency to 5.20.0
chore(plugin-restify): send body in event.request
chore(examples): add missing Dockerfile to angular example
* next: chore(plugin-restify): send body in event.request dep: bump bugsnag-android dependency to v5.20.0 chore(examples): add missing Dockerfile to angular example
chore(plugin-express): send body in event.request
React-native test fixture updates
Update react-native cli test fixture versions
Bump bugsnag-android dependency to v5.22.0
djskinner
approved these changes
Apr 5, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changed
Configuration.setMaxReportedThreads(defaulting to 200)bugsnag-android#1607
bugsnag-android#1596
bugsnag-android#1601
cases where file and line number information was not resolving to the correct
locations. This change may result in grouping changes to more correctly
highlight the root cause of an event.
bugsnag-android#1605
bugsnag-android#1606
bugsnag-android#1624
Bugsnag.isStarted()to test whether the Bugsnag client is in the middle of initializing. This can be used to guard uses of the Bugsnag API that are either on separate threads early in the app's start-up and so not guaranteed to be executed afterBugsnag.starthas completed, or where Bugsnag may not have been started at all due to some internal app logic.slack-jallen:#1621
bugsnag-android#1640
bugsnag-android#1633
Bugsnagstatic methods across different threads whilstBugsnag.startis still in-flight. It is now safe to call anyBugsnagstatic method onceBugsnag.starthas begun executing, as access to the client singleton is controlled by a lock, so the newisStartedmethod (see above) should only be required where it cannot be determined whether the call toBugsnag.starthas begun or you do not want to wait.bugsnag_event_set_contextwith NULLcontextcorrectly clears the event context againbugsnag-android#1637
Fixed
event.request.bodyrather thanevent.metadata.request.body#1702