@sendoracloud/sdk-react-native 0.18.8 → 0.19.0

package/dist/index.cjs

@@ -1830,7 +1830,7 @@ var SendoraSDK = class {
         throw new Error("[sendoracloud] push token metadata exceeds 4KB.");
       }
     }
-    const data = await post(
+    const res = await post(
       { apiUrl: this.config.apiUrl, publicKey: this.config.publicKey, debug: this.debug },
       "/api/v1/push/tokens",
       {
@@ -1843,6 +1843,11 @@ var SendoraSDK = class {
         metadata: reg.metadata ?? {}
       }
     );
+    if (!res || !res.ok) {
+      throw new Error(`[sendoracloud] push token registration failed (HTTP ${res?.status ?? "network"}).`);
+    }
+    const parsed = await res.json();
+    const data = parsed?.data;
     if (!data?.tokenId) {
       throw new Error("[sendoracloud] push token registered but server returned no tokenId \u2014 upgrade backend to >= s58.16.");
     }
@@ -1853,6 +1858,14 @@ var SendoraSDK = class {
    * `sendora.push.registerToken(...)` works consistently across all 5 SDKs.
    * Backed by the same registerPushToken() implementation; kept top-level
    * too for backwards compatibility with the s47 release.
+   *
+   * Tier 3 (s58.70): added `liveActivities.startToken()` and
+   * `geofences.{list,recordEvent}()`. These are JS-side shims around
+   * the backend wire calls — the native bridge work (ActivityKit on
+   * iOS, CoreLocation geofencing, Android NotificationCompat + Geo
+   * APIs) still lives in your app code. Once your native side has
+   * the activity push token / geofence trigger in hand, hand it to
+   * the SDK and we'll persist + dispatch server-side.
    */
   get push() {
     const self = this;
@@ -1867,6 +1880,88 @@ var SendoraSDK = class {
           "/push/track-open",
           body
         );
+      },
+      liveActivities: {
+        /**
+         * Report a freshly-started iOS Live Activity (or Android Live
+         * Update on Android 14+) push token to Sendora so server-side
+         * `PATCH /push/live-activities/:id/update` calls can dispatch
+         * via APNs (iOS) or FCM data-only (Android).
+         *
+         * Host app calls this once per Activity lifecycle, right
+         * after `Activity.pushTokenUpdates` (iOS) or your Android
+         * NotificationCompat setup hands you the push token.
+         */
+        startToken: async (input) => {
+          if (!self.config) throw new Error("[sendoracloud] init() must complete before push.liveActivities.startToken().");
+          const res = await post(
+            { apiUrl: self.config.apiUrl, publicKey: self.config.publicKey, debug: self.debug },
+            "/push/live-activities/start-token",
+            {
+              pushToken: input.pushToken,
+              activityType: input.activityType,
+              platform: input.platform ?? "ios",
+              externalId: input.externalId,
+              userId: input.userId,
+              attributes: input.attributes ?? {},
+              contentState: input.contentState ?? {},
+              bundleId: input.bundleId
+            }
+          );
+          if (!res || !res.ok) {
+            throw new Error(`[sendoracloud] live-activity start-token failed (HTTP ${res?.status ?? "network"}).`);
+          }
+          const parsed = await res.json();
+          const data = parsed?.data;
+          if (!data?.id) throw new Error("[sendoracloud] live-activity start-token: server returned no id.");
+          return { id: data.id, status: data.status ?? "active" };
+        }
+      },
+      geofences: {
+        /**
+         * Fetch the enabled geofences for this device. The SDK doesn't
+         * register them with the OS — that's app-side native work
+         * (CLLocationManager.startMonitoring on iOS, GeofencingClient
+         * on Android). Sort order is server-controlled by priority
+         * asc so the caller can clamp to the OS cap (iOS 20, Android
+         * 100) by truncating the list.
+         */
+        list: async () => {
+          if (!self.config) throw new Error("[sendoracloud] init() must complete before push.geofences.list().");
+          const res = await getJson(
+            { apiUrl: self.config.apiUrl, publicKey: self.config.publicKey, debug: self.debug },
+            "/push/geofences/list-for-device"
+          );
+          if (!res || !res.ok) {
+            throw new Error(`[sendoracloud] geofences list failed (HTTP ${res?.status ?? "network"}).`);
+          }
+          const parsed = await res.json();
+          return parsed?.data ?? [];
+        },
+        /**
+         * Report a geofence enter / exit / dwell event. Backend writes
+         * a `geofence.<kind>` event row + fires any workflows triggered
+         * on that geofence id. Call from the native handler that
+         * receives the OS region notification.
+         */
+        recordEvent: async (input) => {
+          if (!self.config) throw new Error("[sendoracloud] init() must complete before push.geofences.recordEvent().");
+          const res = await post(
+            { apiUrl: self.config.apiUrl, publicKey: self.config.publicKey, debug: self.debug },
+            "/push/geofences/event",
+            {
+              geofenceId: input.geofenceId,
+              kind: input.kind,
+              lat: input.lat,
+              lng: input.lng,
+              accuracyMeters: input.accuracyMeters,
+              dwellSeconds: input.dwellSeconds
+            }
+          );
+          if (!res || !res.ok) {
+            throw new Error(`[sendoracloud] geofence event failed (HTTP ${res?.status ?? "network"}).`);
+          }
+        }
       }
     };
   }

package/dist/index.d.cts

@@ -759,10 +759,54 @@ declare class SendoraSDK {
      * `sendora.push.registerToken(...)` works consistently across all 5 SDKs.
      * Backed by the same registerPushToken() implementation; kept top-level
      * too for backwards compatibility with the s47 release.
+     *
+     * Tier 3 (s58.70): added `liveActivities.startToken()` and
+     * `geofences.{list,recordEvent}()`. These are JS-side shims around
+     * the backend wire calls — the native bridge work (ActivityKit on
+     * iOS, CoreLocation geofencing, Android NotificationCompat + Geo
+     * APIs) still lives in your app code. Once your native side has
+     * the activity push token / geofence trigger in hand, hand it to
+     * the SDK and we'll persist + dispatch server-side.
      */
     get push(): {
         registerToken: (reg: PushTokenRegistration) => Promise<PushTokenReceipt>;
         trackOpen: (sendId: string, clickAction?: string) => Promise<void>;
+        liveActivities: {
+            startToken: (input: {
+                pushToken: string;
+                activityType: string;
+                platform?: "ios" | "android";
+                externalId?: string;
+                userId?: string;
+                attributes?: Record<string, unknown>;
+                contentState?: Record<string, unknown>;
+                bundleId?: string;
+            }) => Promise<{
+                id: string;
+                status: string;
+            }>;
+        };
+        geofences: {
+            list: () => Promise<Array<{
+                id: string;
+                name: string;
+                lat: number;
+                lng: number;
+                radiusMeters: number;
+                priority: number;
+                enabled: boolean;
+                triggerOn: string[];
+                properties?: Record<string, unknown>;
+            }>>;
+            recordEvent: (input: {
+                geofenceId: string;
+                kind: "enter" | "exit" | "dwell";
+                lat?: number;
+                lng?: number;
+                accuracyMeters?: number;
+                dwellSeconds?: number;
+            }) => Promise<void>;
+        };
     };
     /**
      * Attribution namespace — mobile install + deferred deep-link reporting.

package/dist/index.d.ts

@@ -759,10 +759,54 @@ declare class SendoraSDK {
      * `sendora.push.registerToken(...)` works consistently across all 5 SDKs.
      * Backed by the same registerPushToken() implementation; kept top-level
      * too for backwards compatibility with the s47 release.
+     *
+     * Tier 3 (s58.70): added `liveActivities.startToken()` and
+     * `geofences.{list,recordEvent}()`. These are JS-side shims around
+     * the backend wire calls — the native bridge work (ActivityKit on
+     * iOS, CoreLocation geofencing, Android NotificationCompat + Geo
+     * APIs) still lives in your app code. Once your native side has
+     * the activity push token / geofence trigger in hand, hand it to
+     * the SDK and we'll persist + dispatch server-side.
      */
     get push(): {
         registerToken: (reg: PushTokenRegistration) => Promise<PushTokenReceipt>;
         trackOpen: (sendId: string, clickAction?: string) => Promise<void>;
+        liveActivities: {
+            startToken: (input: {
+                pushToken: string;
+                activityType: string;
+                platform?: "ios" | "android";
+                externalId?: string;
+                userId?: string;
+                attributes?: Record<string, unknown>;
+                contentState?: Record<string, unknown>;
+                bundleId?: string;
+            }) => Promise<{
+                id: string;
+                status: string;
+            }>;
+        };
+        geofences: {
+            list: () => Promise<Array<{
+                id: string;
+                name: string;
+                lat: number;
+                lng: number;
+                radiusMeters: number;
+                priority: number;
+                enabled: boolean;
+                triggerOn: string[];
+                properties?: Record<string, unknown>;
+            }>>;
+            recordEvent: (input: {
+                geofenceId: string;
+                kind: "enter" | "exit" | "dwell";
+                lat?: number;
+                lng?: number;
+                accuracyMeters?: number;
+                dwellSeconds?: number;
+            }) => Promise<void>;
+        };
     };
     /**
      * Attribution namespace — mobile install + deferred deep-link reporting.

package/dist/index.js

@@ -1792,7 +1792,7 @@ var SendoraSDK = class {
         throw new Error("[sendoracloud] push token metadata exceeds 4KB.");
       }
     }
-    const data = await post(
+    const res = await post(
       { apiUrl: this.config.apiUrl, publicKey: this.config.publicKey, debug: this.debug },
       "/api/v1/push/tokens",
       {
@@ -1805,6 +1805,11 @@ var SendoraSDK = class {
         metadata: reg.metadata ?? {}
       }
     );
+    if (!res || !res.ok) {
+      throw new Error(`[sendoracloud] push token registration failed (HTTP ${res?.status ?? "network"}).`);
+    }
+    const parsed = await res.json();
+    const data = parsed?.data;
     if (!data?.tokenId) {
       throw new Error("[sendoracloud] push token registered but server returned no tokenId \u2014 upgrade backend to >= s58.16.");
     }
@@ -1815,6 +1820,14 @@ var SendoraSDK = class {
    * `sendora.push.registerToken(...)` works consistently across all 5 SDKs.
    * Backed by the same registerPushToken() implementation; kept top-level
    * too for backwards compatibility with the s47 release.
+   *
+   * Tier 3 (s58.70): added `liveActivities.startToken()` and
+   * `geofences.{list,recordEvent}()`. These are JS-side shims around
+   * the backend wire calls — the native bridge work (ActivityKit on
+   * iOS, CoreLocation geofencing, Android NotificationCompat + Geo
+   * APIs) still lives in your app code. Once your native side has
+   * the activity push token / geofence trigger in hand, hand it to
+   * the SDK and we'll persist + dispatch server-side.
    */
   get push() {
     const self = this;
@@ -1829,6 +1842,88 @@ var SendoraSDK = class {
           "/push/track-open",
           body
         );
+      },
+      liveActivities: {
+        /**
+         * Report a freshly-started iOS Live Activity (or Android Live
+         * Update on Android 14+) push token to Sendora so server-side
+         * `PATCH /push/live-activities/:id/update` calls can dispatch
+         * via APNs (iOS) or FCM data-only (Android).
+         *
+         * Host app calls this once per Activity lifecycle, right
+         * after `Activity.pushTokenUpdates` (iOS) or your Android
+         * NotificationCompat setup hands you the push token.
+         */
+        startToken: async (input) => {
+          if (!self.config) throw new Error("[sendoracloud] init() must complete before push.liveActivities.startToken().");
+          const res = await post(
+            { apiUrl: self.config.apiUrl, publicKey: self.config.publicKey, debug: self.debug },
+            "/push/live-activities/start-token",
+            {
+              pushToken: input.pushToken,
+              activityType: input.activityType,
+              platform: input.platform ?? "ios",
+              externalId: input.externalId,
+              userId: input.userId,
+              attributes: input.attributes ?? {},
+              contentState: input.contentState ?? {},
+              bundleId: input.bundleId
+            }
+          );
+          if (!res || !res.ok) {
+            throw new Error(`[sendoracloud] live-activity start-token failed (HTTP ${res?.status ?? "network"}).`);
+          }
+          const parsed = await res.json();
+          const data = parsed?.data;
+          if (!data?.id) throw new Error("[sendoracloud] live-activity start-token: server returned no id.");
+          return { id: data.id, status: data.status ?? "active" };
+        }
+      },
+      geofences: {
+        /**
+         * Fetch the enabled geofences for this device. The SDK doesn't
+         * register them with the OS — that's app-side native work
+         * (CLLocationManager.startMonitoring on iOS, GeofencingClient
+         * on Android). Sort order is server-controlled by priority
+         * asc so the caller can clamp to the OS cap (iOS 20, Android
+         * 100) by truncating the list.
+         */
+        list: async () => {
+          if (!self.config) throw new Error("[sendoracloud] init() must complete before push.geofences.list().");
+          const res = await getJson(
+            { apiUrl: self.config.apiUrl, publicKey: self.config.publicKey, debug: self.debug },
+            "/push/geofences/list-for-device"
+          );
+          if (!res || !res.ok) {
+            throw new Error(`[sendoracloud] geofences list failed (HTTP ${res?.status ?? "network"}).`);
+          }
+          const parsed = await res.json();
+          return parsed?.data ?? [];
+        },
+        /**
+         * Report a geofence enter / exit / dwell event. Backend writes
+         * a `geofence.<kind>` event row + fires any workflows triggered
+         * on that geofence id. Call from the native handler that
+         * receives the OS region notification.
+         */
+        recordEvent: async (input) => {
+          if (!self.config) throw new Error("[sendoracloud] init() must complete before push.geofences.recordEvent().");
+          const res = await post(
+            { apiUrl: self.config.apiUrl, publicKey: self.config.publicKey, debug: self.debug },
+            "/push/geofences/event",
+            {
+              geofenceId: input.geofenceId,
+              kind: input.kind,
+              lat: input.lat,
+              lng: input.lng,
+              accuracyMeters: input.accuracyMeters,
+              dwellSeconds: input.dwellSeconds
+            }
+          );
+          if (!res || !res.ok) {
+            throw new Error(`[sendoracloud] geofence event failed (HTTP ${res?.status ?? "network"}).`);
+          }
+        }
       }
     };
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sendoracloud/sdk-react-native",
-  "version": "0.18.8",
+  "version": "0.19.0",
   "description": "Sendora Cloud React Native + Expo SDK — analytics, identity, push-token registration, auth, deep links (Branch / Firebase Dynamic Links parity). Auth + analytics + deep links work in Expo Go; push token registration requires a Dev Client (EAS Build or `npx expo prebuild`).",
   "type": "module",
   "main": "./dist/index.cjs",