yaver-feedback-react-native 0.5.4 → 0.5.5

package/README.md

@@ -574,12 +574,34 @@ YaverFeedback.init({
 });
 ```
 
+## Running Inside the Yaver Mobile App (super-host)
+
+When a third-party app is loaded through Yaver's Hermes-push flow (so the
+Yaver mobile app is the runtime container for your app), the SDK detects
+that situation via the `YaverInfo` native module and **automatically
+no-ops `YaverFeedback.init()`** — no ShakeDetector, no FeedbackModal, no
+BlackBox stream from inside the guest. The user only ever sees Yaver's
+native shake overlay ("Reload" + "Back to Yaver") and uses Yaver's
+built-in feedback flow instead.
+
+Standalone installs (TestFlight / App Store / Play from your own dev
+account) are unaffected — the SDK behaves exactly as it did before.
+
+If you need to opt out of the auto-suppression in a specific build (for
+example, to compare behaviour in a super-host smoke test), set
+`enabled: true` explicitly — the Yaver-host gate runs before the
+`enabled` flag is evaluated on purpose.
+
 ## Trigger Modes
 
 ### Shake (default)
 
 Shake the device to open the feedback modal. Uses the built-in shake event on iOS and `ShakeEvent` on Android.
 
+When the app is loaded inside the Yaver mobile app (super-host), the
+SDK yields shake handling to Yaver's native overlay — see the
+"Running Inside the Yaver Mobile App" section above.
+
 ```typescript
 YaverFeedback.init({ authToken, trigger: 'shake' });
 ```

package/dist/ShakeDetector.js

@@ -2,6 +2,22 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.ShakeDetector = void 0;
 const react_native_1 = require("react-native");
+// Detects that the surrounding runtime is Yaver's super-host bridge. The
+// YaverInfo native module is only registered inside Yaver's container
+// (see mobile/ios/Yaver/YaverInfo.{swift,m} and the Android equivalent),
+// so it is undefined in a standalone third-party app. When the SDK runs
+// inside Yaver we yield shake handling to Yaver's native
+// ShakeDetectingWindow — the user should only ever see the 2-button
+// "Reload / Back to Yaver" overlay, never a FeedbackModal popped from
+// inside the guest bundle.
+function isRunningInsideYaverHost() {
+    try {
+        return !!react_native_1.NativeModules?.YaverInfo;
+    }
+    catch {
+        return false;
+    }
+}
 const SHAKE_TIMEOUT_MS = 1000; // minimum time between shakes
 const ACCEL_THRESHOLD_G = 1.8; // peak g-force that qualifies as a shake event
 const ACCEL_MIN_HITS = 3; // peaks within the window before we fire
@@ -34,6 +50,12 @@ class ShakeDetector {
     }
     start(onShake) {
         this.stop();
+        // When the app is loaded inside Yaver's super-host (Hermes push),
+        // Yaver owns the shake gesture and shows its own "Reload / Back to
+        // Yaver" overlay. We must not also fire the guest-side callback,
+        // otherwise the user gets both UIs at once.
+        if (isRunningInsideYaverHost())
+            return;
         this.subscribeDevMenu(onShake);
         this.subscribeAccelerometer(onShake);
     }

package/dist/YaverFeedback.js

@@ -1,11 +1,34 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.YaverFeedback = void 0;
+const react_native_1 = require("react-native");
 const Discovery_1 = require("./Discovery");
 const BlackBox_1 = require("./BlackBox");
 const P2PClient_1 = require("./P2PClient");
 const ShakeDetector_1 = require("./ShakeDetector");
 const auth_1 = require("./auth");
+// Is this JS runtime the Yaver mobile app's super-host bridge? The
+// YaverInfo native module is only registered inside Yaver's container
+// (mobile/ios/Yaver/YaverInfo.{swift,m} + Android counterpart); a
+// standalone app bundled by its own developer has no such module.
+// When the SDK is loaded through Yaver's Hermes-push guest runtime we
+// deliberately no-op every public entry point — Yaver owns the shake
+// gesture ("Reload / Back to Yaver" overlay), the feedback capture
+// flow, and the BlackBox streaming; running a second copy from inside
+// the guest just produces duplicate UIs and double P2P sessions.
+function isRunningInsideYaverHost() {
+    try {
+        return !!react_native_1.NativeModules?.YaverInfo;
+    }
+    catch {
+        return false;
+    }
+}
+// Suppresses SDK activation when inside Yaver super-host. Callers of
+// YaverFeedback.init / startReport / startBatchRecording / … early-out
+// by checking this first so the SDK's side effects (accelerometer,
+// BlackBox HTTP, SSE command channel, FeedbackModal mount) never start.
+const YAVER_HOST_SUPPRESS = isRunningInsideYaverHost();
 let config = null;
 let enabled = false;
 let p2pClient = null;
@@ -34,6 +57,11 @@ class YaverFeedback {
      * via `YaverDiscovery` on the first `startReport()` call.
      */
     static init(cfg) {
+        if (YAVER_HOST_SUPPRESS) {
+            // Running inside Yaver's super-host — yield to Yaver's native UX.
+            enabled = false;
+            return;
+        }
         config = {
             trigger: 'shake',
             maxRecordingDuration: 120,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "yaver-feedback-react-native",
-  "version": "0.5.4",
+  "version": "0.5.5",
   "description": "Visual feedback SDK for Yaver — bug reports, screen recording, voice annotations, and local-first developer workflows",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/src/ShakeDetector.ts

@@ -1,4 +1,20 @@
-import { DeviceEventEmitter, Platform } from 'react-native';
+import { DeviceEventEmitter, NativeModules, Platform } from 'react-native';
+
+// Detects that the surrounding runtime is Yaver's super-host bridge. The
+// YaverInfo native module is only registered inside Yaver's container
+// (see mobile/ios/Yaver/YaverInfo.{swift,m} and the Android equivalent),
+// so it is undefined in a standalone third-party app. When the SDK runs
+// inside Yaver we yield shake handling to Yaver's native
+// ShakeDetectingWindow — the user should only ever see the 2-button
+// "Reload / Back to Yaver" overlay, never a FeedbackModal popped from
+// inside the guest bundle.
+function isRunningInsideYaverHost(): boolean {
+  try {
+    return !!(NativeModules as any)?.YaverInfo;
+  } catch {
+    return false;
+  }
+}
 
 const SHAKE_TIMEOUT_MS = 1000; // minimum time between shakes
 const ACCEL_THRESHOLD_G = 1.8; // peak g-force that qualifies as a shake event
@@ -32,6 +48,11 @@ export class ShakeDetector {
 
   start(onShake: () => void): void {
     this.stop();
+    // When the app is loaded inside Yaver's super-host (Hermes push),
+    // Yaver owns the shake gesture and shows its own "Reload / Back to
+    // Yaver" overlay. We must not also fire the guest-side callback,
+    // otherwise the user gets both UIs at once.
+    if (isRunningInsideYaverHost()) return;
     this.subscribeDevMenu(onShake);
     this.subscribeAccelerometer(onShake);
   }

package/src/YaverFeedback.ts

@@ -1,3 +1,4 @@
+import { NativeModules } from 'react-native';
 import { FeedbackConfig, CapturedError } from './types';
 import { YaverDiscovery } from './Discovery';
 import { BlackBox } from './BlackBox';
@@ -12,6 +13,29 @@ import {
   DEFAULT_CONVEX_SITE_URL,
 } from './auth';
 
+// Is this JS runtime the Yaver mobile app's super-host bridge? The
+// YaverInfo native module is only registered inside Yaver's container
+// (mobile/ios/Yaver/YaverInfo.{swift,m} + Android counterpart); a
+// standalone app bundled by its own developer has no such module.
+// When the SDK is loaded through Yaver's Hermes-push guest runtime we
+// deliberately no-op every public entry point — Yaver owns the shake
+// gesture ("Reload / Back to Yaver" overlay), the feedback capture
+// flow, and the BlackBox streaming; running a second copy from inside
+// the guest just produces duplicate UIs and double P2P sessions.
+function isRunningInsideYaverHost(): boolean {
+  try {
+    return !!(NativeModules as any)?.YaverInfo;
+  } catch {
+    return false;
+  }
+}
+
+// Suppresses SDK activation when inside Yaver super-host. Callers of
+// YaverFeedback.init / startReport / startBatchRecording / … early-out
+// by checking this first so the SDK's side effects (accelerometer,
+// BlackBox HTTP, SSE command channel, FeedbackModal mount) never start.
+const YAVER_HOST_SUPPRESS = isRunningInsideYaverHost();
+
 let config: FeedbackConfig | null = null;
 let enabled = false;
 let p2pClient: P2PClient | null = null;
@@ -44,6 +68,11 @@ export class YaverFeedback {
    * via `YaverDiscovery` on the first `startReport()` call.
    */
   static init(cfg: FeedbackConfig): void {
+    if (YAVER_HOST_SUPPRESS) {
+      // Running inside Yaver's super-host — yield to Yaver's native UX.
+      enabled = false;
+      return;
+    }
     config = {
       trigger: 'shake',
       maxRecordingDuration: 120,