Merge pull request #1711 from bugsnag/android-5220

Bump bugsnag-android dependency to v5.22.0

Author: lemnik

CHANGELOG.md

@@ -4,12 +4,29 @@
 
 ### Changed
 
-- (react-native) Update bugsnag-android to v5.20.0
+- (react-native) Update bugsnag-android to v5.22.0
   - The number of threads reported can now be limited using `Configuration.setMaxReportedThreads` (defaulting to 200)
     [bugsnag-android#1607](https://github.com/bugsnag/bugsnag-android/pull/1607)
   - Improved the performance and stability of the NDK and ANR plugins by caching JNI references on start
     [bugsnag-android#1596](https://github.com/bugsnag/bugsnag-android/pull/1596)
     [bugsnag-android#1601](https://github.com/bugsnag/bugsnag-android/pull/1601)
+  - 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.
+    [bugsnag-android#1605](https://github.com/bugsnag/bugsnag-android/pull/1605)
+    [bugsnag-android#1606](https://github.com/bugsnag/bugsnag-android/pull/1606)
+  - Fixed an issue where an uncaught exception on the main thread could in rare cases trigger an ANR.
+    [bugsnag-android#1624](https://github.com/bugsnag/bugsnag-android/pull/1624)
+  - 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](https://github.com/slack-jallen):[#1621](https://github.com/bugsnag/bugsnag-android/pull/1621)
+    [bugsnag-android#1640](https://github.com/bugsnag/bugsnag-android/pull/1640)
+  - Events and Sessions will be discarded if they cannot be uploaded and are older than 60 days or larger than 1MB
+    [bugsnag-android#1633](https://github.com/bugsnag/bugsnag-android/pull/1633)
+  - Fixed potentially [thread-unsafe access](https://github.com/bugsnag/bugsnag-android/issues/883) 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.
+  - [bugsnag-android#1638](https://github.com/bugsnag/bugsnag-android/pull/1638)
+  - Calling `bugsnag_event_set_context` with NULL `context` correctly clears the event context again
+    [bugsnag-android#1637](https://github.com/bugsnag/bugsnag-android/pull/1637)
 
 ### Fixed
 

packages/react-native/android/build.gradle

@@ -39,8 +39,8 @@ android {
 }
 
 dependencies {
-    api "com.bugsnag:bugsnag-android:5.20.0"
-    api "com.bugsnag:bugsnag-plugin-react-native:5.20.0"
+    api "com.bugsnag:bugsnag-android:5.22.0"
+    api "com.bugsnag:bugsnag-plugin-react-native:5.22.0"
     implementation 'com.facebook.react:react-native:+'
 
     testImplementation "junit:junit:4.12"

packages/react-native/prepare-android-vendor.config

@@ -1,2 +1,2 @@
 version
-5.20.0
+5.22.0