chore: update expo-updates to use a patch for bridgeless crash fix

Author: gkartalis

.yarn/patches/expo-updates-npm-55.0.21-990b55bddd.patch

@@ -0,0 +1,43 @@
+diff --git a/android/src/main/java/expo/modules/updates/errorrecovery/ErrorRecovery.kt b/android/src/main/java/expo/modules/updates/errorrecovery/ErrorRecovery.kt
+index c216e1cfaff3b6c0bcae4f0fd68f02cadac7aabd..702735099c49f811caae7f71ce9291f9f6c7104a 100644
+--- a/android/src/main/java/expo/modules/updates/errorrecovery/ErrorRecovery.kt
++++ b/android/src/main/java/expo/modules/updates/errorrecovery/ErrorRecovery.kt
+@@ -29,6 +29,7 @@ class ErrorRecovery(
+   internal lateinit var handler: Handler
+ 
+   private var shouldHandleReactInstanceException = false
++  private var previousBridgelessExceptionHandler: ((Exception) -> Unit)? = null
+ 
+   fun initialize(delegate: ErrorRecoveryDelegate) {
+     if (!::handler.isInitialized) {
+@@ -49,6 +50,13 @@ class ErrorRecovery(
+   internal fun onReactInstanceException(exception: Exception) {
+     if (shouldHandleReactInstanceException) {
+       handleException(exception)
++    } else if (previousBridgelessExceptionHandler != null) {
++      // PATCHED: Instead of silently ignoring, pass to fallback handler
++      try {
++        previousBridgelessExceptionHandler?.invoke(exception)
++      } catch (e: Exception) {
++        logger.error("Error in bridgeless exception fallback handler", e, UpdatesErrorCode.Unknown)
++      }
+     }
+   }
+ 
+@@ -92,9 +100,16 @@ class ErrorRecovery(
+ 
+   private fun registerErrorHandler(devSupportManager: DevSupportManager) {
+     shouldHandleReactInstanceException = true
++    // PATCHED: Store the current default uncaught exception handler as fallback
++    previousBridgelessExceptionHandler = { exception ->
++      Thread.getDefaultUncaughtExceptionHandler()?.uncaughtException(Thread.currentThread(), exception)
++    }
+   }
+ 
+   private fun unregisterErrorHandler() {
+     shouldHandleReactInstanceException = false
++    // PATCHED: Do NOT clear previousBridgelessExceptionHandler
++    // Keep it active so crashes after 10s are still passed to the fallback handler
++    // instead of being silently ignored. This is the core fix for the Bridgeless crash issue.
+   }
+ }

HACKS.md

@@ -286,3 +286,13 @@ Another dependency in the Expo/react-native ecosystem has brought in com.caveroc
 #### When can we remove this:
 
 When the upstream @d11/react-native-fast-image closes and releases this PR https://github.com/dream-horizon-org/react-native-fast-image/pull/354/changes
+
+## patch for expo-updates
+
+#### Explanation/Context:
+
+Started seeing blank screens on android when app was crashing instead of regularly crashing the app after we enabled new architecture. This patch attempts to fix that.
+
+#### When can we remove this:
+
+When the upstream expo-updates repository fixes the issue and releases a new version that properly handles crashes on Android with the new architecture. https://github.com/expo/expo/issues/41543

package.json

@@ -155,7 +155,7 @@
     "expo": "^55.0.0",
     "expo-build-properties": "55.0.13",
     "expo-navigation-bar": "55.0.12",
-    "expo-updates": "55.0.21",
+    "expo-updates": "patch:expo-updates@npm%3A55.0.21#~/.yarn/patches/expo-updates-npm-55.0.21-990b55bddd.patch",
     "formik": "2.2.9",
     "html-entities": "2.3.3",
     "jwt-decode": "4.0.0",

yarn.lock

@@ -13477,7 +13477,7 @@ __metadata:
     expo-build-disk-cache: "patch:expo-build-disk-cache@npm%3A0.7.2#~/.yarn/patches/expo-build-disk-cache-npm-0.7.2-c51a562767.patch"
     expo-build-properties: "npm:55.0.13"
     expo-navigation-bar: "npm:55.0.12"
-    expo-updates: "npm:55.0.21"
+    expo-updates: "patch:expo-updates@npm%3A55.0.21#~/.yarn/patches/expo-updates-npm-55.0.21-990b55bddd.patch"
     formik: "npm:2.2.9"
     graphql: "npm:16.8.1"
     graphql-request: "npm:5.1.0"
@@ -15010,6 +15010,34 @@ __metadata:
   languageName: node
   linkType: hard
 
+"expo-updates@patch:expo-updates@npm%3A55.0.21#~/.yarn/patches/expo-updates-npm-55.0.21-990b55bddd.patch":
+  version: 55.0.21
+  resolution: "expo-updates@patch:expo-updates@npm%3A55.0.21#~/.yarn/patches/expo-updates-npm-55.0.21-990b55bddd.patch::version=55.0.21&hash=c07c93"
+  dependencies:
+    "@expo/code-signing-certificates": "npm:^0.0.6"
+    "@expo/plist": "npm:^0.5.2"
+    "@expo/spawn-async": "npm:^1.7.2"
+    arg: "npm:^4.1.0"
+    chalk: "npm:^4.1.2"
+    debug: "npm:^4.3.4"
+    expo-eas-client: "npm:~55.0.5"
+    expo-manifests: "npm:~55.0.16"
+    expo-structured-headers: "npm:~55.0.2"
+    expo-updates-interface: "npm:~55.1.6"
+    getenv: "npm:^2.0.0"
+    glob: "npm:^13.0.0"
+    ignore: "npm:^5.3.1"
+    resolve-from: "npm:^5.0.0"
+  peerDependencies:
+    expo: "*"
+    react: "*"
+    react-native: "*"
+  bin:
+    expo-updates: bin/cli.js
+  checksum: 10c0/37f5afe711978847308db050376a999680c4b2e6964407f83212ef958f6c61878a87af20ea0943e882a4a5d16ed75bb5d765f0dc7765f87cf6622552c2175952
+  languageName: node
+  linkType: hard
+
 "expo@npm:^55.0.0":
   version: 55.0.23
   resolution: "expo@npm:55.0.23"