v5.22.0 #1643
Merged
v5.22.0 #1643
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
Optimize CI a bit
Clear app data before all e2e tests
`bsg_strncpy` should terminate `dst` even if `src` is `NULL`
… functions are safe to call while `Bugsnag.start` is still running
…safety Improve `Bugsnag.start` thread-safety
Ensure handling_crash flag is atomic
…session payloads based on age
[PLAT-8191] Add Bugsnag.isStarted
…n the non-startup thread, to simulate some typical startup work-load (but not long enough for `Bugsnag.start` to complete)
[PLAT-8185] Limit retries of event payloads based on size and age, and session payloads based on age
…eading Fix MultiThreadedStartupScenario
Consistently format e2e test feature files
Rename Cucumber step for consistency with Cocoa
tomlongridge
approved these changes
Mar 31, 2022
lemnik
force-pushed
the
releases/v5.22.0
branch
from
f307046
to
eeb518a
Compare
Android notifier sizes
Generated by 🚫 Danger |
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.
Enhancements
Added
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
#1640
Events and Sessions will be discarded if they cannot be uploaded and are older than 60 days or larger than 1MB
#1633
Bug fixes
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. #1638bugsnag_event_set_contextwith NULLcontextcorrectly clears the event context again#1637