Bugsnag v5.22.0 Release Notes

Release Date: 2022-03-31 // 3 months ago
  • ✨ 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 after Bugsnag.start has 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

    • Fixed potentially thread-unsafe access when invoking Bugsnag static methods across different threads whilst Bugsnag.start is still in-flight. It is now safe to call any Bugsnag static method once Bugsnag.start has begun executing, as access to the client singleton is controlled by a lock, so the new isStarted method (see above) should only be required where it cannot be determined whether the call to Bugsnag.start has begun or you do not want to wait. #1638
    • Calling bugsnag_event_set_context with NULL context correctly clears the event context again #1637