@scalebun/react-native 1.10.1 → 1.10.3

package/android/src/main/java/com/scalebun/rn/crash/ScaleBunCrashModule.kt

@@ -3,6 +3,7 @@ package com.scalebun.rn.crash
 import com.facebook.react.bridge.*
 import com.scalebun.core.crash.CrashStorage
 import com.scalebun.core.crash.NativeCrashHandler
+import org.json.JSONObject
 
 /**
  * React Native bridge for native crash capture.
@@ -161,4 +162,27 @@ class ScaleBunCrashModule(reactContext: ReactApplicationContext) :
             promise.reject("CRASH_DRAIN_ERROR", e.message, e)
         }
     }
+
+    /**
+     * Persist a FATAL JS crash to the same store native crashes use.
+     *
+     * BLOCKING SYNCHRONOUS on purpose. A fatal JS error unwinds the process, and
+     * an async promise call would return before the write ran — losing the crash,
+     * which is exactly the bug this closes. A synchronous write finishes on disk
+     * before the JS handler returns, so the next launch drains it via
+     * drainPendingCrash like any native crash.
+     *
+     * Never throws: it runs while the app is already dying, and the crashId in the
+     * record makes the eventual delivery idempotent.
+     */
+    @ReactMethod(isBlockingSynchronousMethod = true)
+    override fun persistJsCrash(recordJson: String?): Boolean {
+        return try {
+            if (recordJson.isNullOrEmpty()) return false
+            CrashStorage.write(reactApplicationContext.applicationContext, JSONObject(recordJson))
+            true
+        } catch (e: Exception) {
+            false
+        }
+    }
 }

package/android/src/oldarch/java/com/scalebun/rn/crash/ScaleBunCrashSpec.kt

@@ -34,4 +34,7 @@ abstract class ScaleBunCrashSpec(reactContext: ReactApplicationContext) :
      */
     abstract fun setActiveSessionId(sessionId: String?, promise: Promise)
     abstract fun clearPendingCrash(crashId: String?, promise: Promise)
+
+    // Synchronous: returns a value, so no Promise. See the module for why.
+    abstract fun persistJsCrash(recordJson: String?): Boolean
 }