@logbrew/react-native 0.1.2 → 0.1.4

package/LogBrewReactNative.podspec

@@ -0,0 +1,22 @@
+require "json"
+
+package = JSON.parse(File.read(File.join(__dir__, "package.json")))
+
+Pod::Spec.new do |spec|
+  spec.name = "LogBrewReactNative"
+  spec.version = package["version"]
+  spec.summary = package["description"]
+  spec.homepage = "https://github.com/LogBrewCo/sdk"
+  spec.license = package["license"]
+  spec.authors = { "LogBrew" => "opensource@logbrew.com" }
+  spec.platforms = { :ios => "13.0" }
+  spec.source = {
+    :git => "https://github.com/LogBrewCo/sdk.git",
+    :tag => "react-native-v#{spec.version}"
+  }
+  spec.source_files = "ios/**/*.{h,m,mm}"
+  spec.exclude_files = "ios/Tests/**/*"
+  spec.dependency "React-Core"
+
+  install_modules_dependencies(spec) if respond_to?(:install_modules_dependencies, true)
+end

package/README.md

@@ -106,7 +106,7 @@ try {
 
 Set `includeStack: true` only when your app has decided stack text is safe to send. Non-`Error` thrown values are accepted and converted into issue messages so app error handlers do not need custom guards.
 
-### Reversible nonfatal global reports
+### Reversible global JavaScript reports
 
 Install the optional global JavaScript handler before root registration when you want supported nonfatal `ErrorUtils` failures captured without an app-owned capture call:
 
@@ -126,9 +126,9 @@ errorHandler.remove();
 
 Installation is idempotent for the active React Native `ErrorUtils` object. The wrapper captures a fixed-content, path-bounded issue for nonfatal global JavaScript errors and then calls the handler that was installed before it. Capture and diagnostic callback failures cannot prevent that prior handler from running. `remove()` reinstates the previous handler only while LogBrew still owns the global slot, so a later integration is not overwritten.
 
-Fatal JavaScript errors are chained without capture. The JavaScript package has no synchronous native durable handoff and does not retain fatal events across process termination. Fatal replay requires a bounded synchronous native store plus next-launch delivery acknowledgement. Unhandled Promise rejections are not installed or patched because React Native does not expose one stable supported ownership seam across its runtimes.
+The React Native conditional export obtains LogBrew's synchronous native fatal store through the supported TurboModule or `NativeModules` seam. Before chaining a fatal report, it writes one bounded record to app-private storage that is excluded from operating-system archives. On a later installation it performs stable-ID at-least-once replay, and acknowledgement happens only after local queue admission is observable through the SDK queue counters. Filtered, dropped, unknown-admission, persistence-failed, and acknowledgement-failed records are retained. A failed acknowledgement is retried without admitting the same ID twice in one JavaScript runtime. Use `fatalHealth()` for frozen bounded counters and status, or `discardPendingFatalRecord()` for an explicit rollback discard. The Node ESM and CommonJS entries never import React Native; non-React-Native callers must inject `fatalStore` explicitly.
 
-Automatic events exclude the original error message, raw stack, arbitrary metadata, full URLs, hosts, query strings, and local absolute paths. `onDiagnostic` receives only a fixed code. This integration does not provide native crash capture, ANR/watchdog capture, fatal persistence, or exactly-once fatal replay.
+Automatic events exclude the original error message, raw stack, arbitrary metadata, full URLs, hosts, query strings, local absolute paths, payloads, and native error text. `onDiagnostic` receives only a fixed code. This integration does not claim mathematically exactly-once delivery, backend-visible deduplication, native crash capture, Promise rejection ownership, ANR or hang detection, general offline queueing, or symbolication. Unhandled Promise rejections are not installed or patched because React Native does not expose one stable supported ownership seam across its runtimes.
 
 When you prepare React Native release artifacts, wrap the app-owned Metro config once. Production bundles and source maps receive one matching Debug ID, while development and hot-reload serialization remain unchanged:
 

package/android/build.gradle

@@ -0,0 +1,42 @@
+def newArchitectureEnabled() {
+  return project.hasProperty("newArchEnabled") && project.newArchEnabled == "true"
+}
+
+apply plugin: "com.android.library"
+
+if (newArchitectureEnabled()) {
+  apply plugin: "com.facebook.react"
+  react {
+    jsRootDir = file("../src")
+    libraryName = "LogBrewReactNativeSpec"
+    codegenJavaPackageName = "co.logbrew.reactnative"
+  }
+}
+
+android {
+  namespace "co.logbrew.reactnative"
+  compileSdkVersion rootProject.ext.has("compileSdkVersion")
+      ? rootProject.ext.get("compileSdkVersion")
+      : 35
+
+  defaultConfig {
+    minSdkVersion rootProject.ext.has("minSdkVersion")
+        ? rootProject.ext.get("minSdkVersion")
+        : 24
+    targetSdkVersion rootProject.ext.has("targetSdkVersion")
+        ? rootProject.ext.get("targetSdkVersion")
+        : 35
+  }
+
+  sourceSets {
+    main {
+      java.srcDirs += newArchitectureEnabled()
+          ? ["src/newarch/java"]
+          : ["src/oldarch/java"]
+    }
+  }
+}
+
+dependencies {
+  implementation "com.facebook.react:react-android"
+}

package/android/src/main/AndroidManifest.xml

@@ -0,0 +1 @@
+<manifest xmlns:android="http://schemas.android.com/apk/res/android" />