@appilots/sdk 0.7.0 → 0.10.0

package/README.md

@@ -15,7 +15,8 @@ pnpm add @appilots/sdk
 ## Quick Start
 
 ```tsx
-import { AppilotsProvider, AppilotsChat } from '@appilots/sdk';
+import { AppilotsProvider, AppilotsNavigationContainer, AppilotsChat } from '@appilots/sdk';
+import { NavigationContainer } from '@react-navigation/native';
 
 function App() {
   return (
@@ -24,15 +25,56 @@ function App() {
         projectId: 'your-project-id',
       }}
     >
-      <NavigationContainer>
-        {/* Your app screens */}
-      </NavigationContainer>
+      <AppilotsNavigationContainer>
+        <NavigationContainer>{/* Your app screens */}</NavigationContainer>
+      </AppilotsNavigationContainer>
       <AppilotsChat />
     </AppilotsProvider>
   );
 }
 ```
 
+## What happens when Appilots breaks
+
+The SDK renders inside your app, so a bug of ours must never become an
+outage of yours. Both render surfaces sit behind an error boundary:
+
+- If the **provider** throws, your app keeps rendering. The assistant
+  goes inert — `AppilotsChat` renders nothing, and `useAppilots()` keeps
+  returning a context (with `degraded: true`) so your own code does not
+  throw either.
+- If the **chat** throws, only the chat disappears.
+- If the **auto-tracking interceptor** throws on some element, that
+  element renders untouched; the agent just does not see it.
+
+In every case we log a `console.error` that says plainly it is our bug,
+not yours, and the failure is reported to the Appilots dashboard on the
+next session so we find out without you having to file anything.
+
+Degradation lasts for the session — a surface that crashed once usually
+crashes again, and an assistant blinking in and out of your product is
+worse than an absent one. An exception thrown by **your** components is
+never swallowed: it propagates to your own error boundary as it would
+without us.
+
+## Native confirmation dialogs
+
+When the user approves a destructive action on the chat's confirm card
+and your code then calls `Alert.alert` to double-check, the SDK answers
+that dialog once on their behalf — otherwise they are asked the same
+question twice and the second dialog is one the agent cannot press.
+
+Doing that means briefly replacing `Alert.alert`, a global that belongs
+to your app. The replacement is refcounted, restored even if the action
+throws, answers at most one dialog, never presses a `style: 'cancel'`
+button, and expires about a second after the press so unrelated alerts
+(background sync, push handlers) are never touched. To turn it off and
+show your own dialog instead:
+
+```tsx
+<AppilotsProvider config={{ projectId: '…', suppressNativeConfirm: false }}>
+```
+
 ## Documentation
 
 Full documentation available at [docs.appilots.com](https://docs.appilots.com)

package/dist/.build-meta.json

@@ -0,0 +1,5 @@
+{
+  "sourceHash": "cb3f70407bf9512b",
+  "gitSha": "00511f555d4bc51c481138de6dc3ad90ce2e60e3",
+  "builtAt": "2026-08-24T18:34:11.310Z"
+}

package/dist/{chunk-KYFAXT6V.js → chunk-2GCWCPSD.js}

@@ -1,6 +1,6 @@
 'use strict';
 
-var chunkDZ7QRFHD_js = require('./chunk-DZ7QRFHD.js');
+var chunkYB77RYCC_js = require('./chunk-YB77RYCC.js');
 var React = require('react');
 
 function _interopDefault (e) { return e && e.__esModule ? e : { default: e }; }
@@ -15,24 +15,27 @@ function getActiveRouteName(state) {
   return route.name;
 }
 function AppilotsNavigationContainer({ children }) {
-  const { emit } = chunkDZ7QRFHD_js.useAppilotsContext();
+  const { emit } = chunkYB77RYCC_js.useAppilotsContext();
   const internalRef = React.useRef(null);
-  const handleRef = React.useCallback((instance) => {
-    internalRef.current = instance;
-    chunkDZ7QRFHD_js.setNavigationRef(instance);
-    const childRef = children.ref;
-    if (typeof childRef === "function") childRef(instance);
-    else if (childRef && typeof childRef === "object") childRef.current = instance;
-    if (instance) {
-      console.log("[Appilots] NavigationContainer ref captured");
-    }
-  }, [children]);
+  const handleRef = React.useCallback(
+    (instance) => {
+      internalRef.current = instance;
+      chunkYB77RYCC_js.setNavigationRef(instance);
+      const childRef = children.ref;
+      if (typeof childRef === "function") childRef(instance);
+      else if (childRef && typeof childRef === "object") childRef.current = instance;
+      if (instance) {
+        chunkYB77RYCC_js.appilotsDebugLog("NavigationContainer ref captured");
+      }
+    },
+    [children]
+  );
   const handleStateChange = React.useCallback(
     (state) => {
       const routeName = getActiveRouteName(state);
       if (routeName) {
-        console.log(`[Appilots] Screen changed \u2192 "${routeName}"`);
-        chunkDZ7QRFHD_js.setCurrentScreen(routeName);
+        chunkYB77RYCC_js.appilotsDebugLog(`Screen changed \u2192 "${routeName}"`);
+        chunkYB77RYCC_js.setCurrentScreen(routeName);
         emit({
           type: "navigation:change",
           timestamp: Date.now(),
@@ -47,8 +50,8 @@ function AppilotsNavigationContainer({ children }) {
     const timer = setTimeout(() => {
       const route = internalRef.current?.getCurrentRoute?.();
       if (route?.name) {
-        console.log(`[Appilots] Initial screen \u2192 "${route.name}"`);
-        chunkDZ7QRFHD_js.setCurrentScreen(route.name);
+        chunkYB77RYCC_js.appilotsDebugLog(`Initial screen \u2192 "${route.name}"`);
+        chunkYB77RYCC_js.setCurrentScreen(route.name);
         emit({
           type: "navigation:change",
           timestamp: Date.now(),