fix(app, android): firebase-android-sdk 29.0.3 to fix underlying NPE …

…in 29.0.2 (#5946)

* fix(deps): firebase-android-sdk 29.0.3
* docs(crashlytics): add anr collection support section
* fix(docs): run the format:markdown command
* fix(docs): fix typo in the ANR doc.
* fix(docs): Add the ANR word in the .spellcheck.dict.txt file

.spellcheck.dict.txt

@@ -4,6 +4,7 @@ Ad
 AdMob
 Analytics
 analytics
+ANR
 APIs
 APIs.
 AppAttest

docs/crashlytics/crash-reports.md

@@ -46,3 +46,14 @@ you to filter it out in the overview by selecting 'Open' under 'Issue state', wh
 This is visible in the first example, where we're displaying only 3 relevant non-fatal events out of the 12 that occurred.
 When the same issue re-occurs, it will automatically open again. By clicking the arrow next to the button we can mute the
 issue, preventing this from happening.
+
+# Android ANR Collection Support
+
+The Firebase Team enabled the ability to collect
+Application Not Responding (ANR) issues that occur when the UI thread of an Android app is blocked for too long,
+for more information on ANR see the
+[android developer documentation](https://developer.android.com/topic/performance/vitals/anr).
+
+The support for ANR collection is added in the Android Crashlytics version
+[18.2.4](https://firebase.google.com/support/release-notes/android#crashlytics_v18-2-4)
+so that your react native application can collect ANR, make sure you are using at least version 13.0.1 of this library

packages/app/package.json

@@ -72,7 +72,7 @@
       "targetSdk": 31,
       "compileSdk": 31,
       "buildTools": "30.0.3",
-      "firebase": "29.0.2",
+      "firebase": "29.0.3",
       "firebaseCrashlyticsGradle": "2.8.1",
       "firebasePerfGradle": "1.4.0",
       "gmsGoogleServicesGradle": "4.3.10",