Bump bugsnag-android-ndk from 4.9.1 to 5.22.0

[dependabot]

Bumps bugsnag-android-ndk from 4.9.1 to 5.22.0.

Release notes

Sourced from bugsnag-android-ndk's releases.

v5.22.0

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

v5.21.0

Enhancements

• Fix inconsistencies in stack trace quality for C/C++ events. Resolves a few 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. #1605 #1606

Bug fixes

• Fixed an issue where an uncaught exception on the main thread could in rare cases trigger an ANR. #1624

v5.20.0

Enhancements

• The number of threads reported can now be limited using Configuration.setMaxReportedThreads (defaulting to 200) #1607

• Improved the performance and stability of the NDK and ANR plugins by caching JNI references on start #1596 #1601

v5.19.2

Bug fixes

• Fixed an issue where feature-flags were not always sent if an OnSendCallback was configured #1589

• Fix a bug where api keys set in React Native callbacks were ignored #1592

... (truncated)

Changelog

Sourced from bugsnag-android-ndk's changelog.

5.22.0 (2022-03-31)

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

5.21.0 (2022-03-17)

Enhancements

• Fix inconsistencies in stack trace quality for C/C++ events. Resolves a few 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. #1605 #1606

Bug fixes

• Fixed an issue where an uncaught exception on the main thread could in rare cases trigger an ANR. #1624

5.20.0 (2022-03-10)

Enhancements

• The number of threads reported can now be limited using Configuration.setMaxReportedThreads (defaulting to 200) #1607

• Improved the performance and stability of the NDK and ANR plugins by caching JNI references on start #1596 #1601

5.19.2 (2022-01-31)

Bug fixes

• Fixed an issue where feature-flags were not always sent if an OnSendCallback was configured #1589

... (truncated)

Commits

• a5824a3 Merge pull request #1643 from bugsnag/releases/v5.22.0
• eeb518a v5.22.0
• c1bea01 Merge pull request #1642 from bugsnag/tms/rename-step
• d2b4928 Rename Cucumber step for consistency with Cocoa
• b4c253d Merge pull request #1635 from bugsnag/tms/reformat-features
• 7c0a730 Consistently format feature files
• 450e931 Merge pull request #1641 from bugsnag/PLAT_8247/fix-bugsnag-start-threading
• 806afbe Merge branch 'next' into PLAT_8247/fix-bugsnag-start-threading
• 51b7eae Merge pull request #1633 from bugsnag/PLAT-8185-delete-old-big-events
• 0dad273 Merge branch 'next' into PLAT_8247/fix-bugsnag-start-threading
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #130.