@sendoracloud/sdk-react-native 1.18.0 → 1.19.0

package/dist/index.cjs

@@ -200,7 +200,7 @@ var Storage = class {
 // package.json
 var package_default = {
   name: "@sendoracloud/sdk-react-native",
-  version: "1.18.0",
+  version: "1.19.0",
   description: "Sendora Cloud React Native + Expo SDK \u2014 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",
@@ -2358,6 +2358,37 @@ var SendoraSDK = class {
   getUserId() {
     return this.userId;
   }
+  /**
+   * Non-throwing, synchronous read of the verified auth principal. Returns
+   * the persisted `AuthUser` (`{ id, email, emailVerified, name, isAnonymous }`)
+   * or `null` when no session is hydrated yet. Zero I/O — a pure in-memory read
+   * of the session restored during `init()` — so it is safe on the very first
+   * API call at cold start: await `init()` once (disk-only, no network), then
+   * read this synchronously, even offline.
+   *
+   * `id` is the JWT `sub` — the durable, server-verified identity to key your
+   * backend data on. Do NOT use `getAnonymousIdSync()` for that (it's a
+   * rotating analytics id). Pair with `isReady()` to tell "still restoring"
+   * apart from "signed out": `null` here while `isReady()` is `false` = init
+   * hasn't finished; `null` while `isReady()` is `true` = genuinely no session.
+   * `isAnonymous` is optional on the wire — test `=== false`, not truthiness.
+   * The access token is re-verified server-side, so reading identity here
+   * (client-untrusted) for UI/routing is safe; never use it as your own
+   * authorization decision.
+   */
+  getUserSync() {
+    return this.ready ? this.auth.getCurrentUser() : null;
+  }
+  /**
+   * Non-throwing, synchronous readiness flag. `true` once `init()` has
+   * resolved (storage hydrated + auth session restored). Gate a cold-start
+   * identity read on this so you never mistake "still restoring the session"
+   * for "signed out" — the loading gate every mobile auth SDK expects
+   * (Firebase's init-null caveat, Clerk's `isLoaded`).
+   */
+  isReady() {
+    return this.ready;
+  }
   /** Toggle consent at runtime — when false, events drop instead of fire. */
   setConsent(granted) {
     this.consentGranted = granted;

package/dist/index.d.cts

@@ -985,6 +985,33 @@ declare class SendoraSDK {
     getAnonymousIdSync(): string | null;
     /** Current identified user id, if any. */
     getUserId(): string | null;
+    /**
+     * Non-throwing, synchronous read of the verified auth principal. Returns
+     * the persisted `AuthUser` (`{ id, email, emailVerified, name, isAnonymous }`)
+     * or `null` when no session is hydrated yet. Zero I/O — a pure in-memory read
+     * of the session restored during `init()` — so it is safe on the very first
+     * API call at cold start: await `init()` once (disk-only, no network), then
+     * read this synchronously, even offline.
+     *
+     * `id` is the JWT `sub` — the durable, server-verified identity to key your
+     * backend data on. Do NOT use `getAnonymousIdSync()` for that (it's a
+     * rotating analytics id). Pair with `isReady()` to tell "still restoring"
+     * apart from "signed out": `null` here while `isReady()` is `false` = init
+     * hasn't finished; `null` while `isReady()` is `true` = genuinely no session.
+     * `isAnonymous` is optional on the wire — test `=== false`, not truthiness.
+     * The access token is re-verified server-side, so reading identity here
+     * (client-untrusted) for UI/routing is safe; never use it as your own
+     * authorization decision.
+     */
+    getUserSync(): AuthUser | null;
+    /**
+     * Non-throwing, synchronous readiness flag. `true` once `init()` has
+     * resolved (storage hydrated + auth session restored). Gate a cold-start
+     * identity read on this so you never mistake "still restoring the session"
+     * for "signed out" — the loading gate every mobile auth SDK expects
+     * (Firebase's init-null caveat, Clerk's `isLoaded`).
+     */
+    isReady(): boolean;
     /** Toggle consent at runtime — when false, events drop instead of fire. */
     setConsent(granted: boolean): void;
     /** Associate a user id + traits with the current anonymous install. */

package/dist/index.d.ts

@@ -985,6 +985,33 @@ declare class SendoraSDK {
     getAnonymousIdSync(): string | null;
     /** Current identified user id, if any. */
     getUserId(): string | null;
+    /**
+     * Non-throwing, synchronous read of the verified auth principal. Returns
+     * the persisted `AuthUser` (`{ id, email, emailVerified, name, isAnonymous }`)
+     * or `null` when no session is hydrated yet. Zero I/O — a pure in-memory read
+     * of the session restored during `init()` — so it is safe on the very first
+     * API call at cold start: await `init()` once (disk-only, no network), then
+     * read this synchronously, even offline.
+     *
+     * `id` is the JWT `sub` — the durable, server-verified identity to key your
+     * backend data on. Do NOT use `getAnonymousIdSync()` for that (it's a
+     * rotating analytics id). Pair with `isReady()` to tell "still restoring"
+     * apart from "signed out": `null` here while `isReady()` is `false` = init
+     * hasn't finished; `null` while `isReady()` is `true` = genuinely no session.
+     * `isAnonymous` is optional on the wire — test `=== false`, not truthiness.
+     * The access token is re-verified server-side, so reading identity here
+     * (client-untrusted) for UI/routing is safe; never use it as your own
+     * authorization decision.
+     */
+    getUserSync(): AuthUser | null;
+    /**
+     * Non-throwing, synchronous readiness flag. `true` once `init()` has
+     * resolved (storage hydrated + auth session restored). Gate a cold-start
+     * identity read on this so you never mistake "still restoring the session"
+     * for "signed out" — the loading gate every mobile auth SDK expects
+     * (Firebase's init-null caveat, Clerk's `isLoaded`).
+     */
+    isReady(): boolean;
     /** Toggle consent at runtime — when false, events drop instead of fire. */
     setConsent(granted: boolean): void;
     /** Associate a user id + traits with the current anonymous install. */

package/dist/index.js

@@ -157,7 +157,7 @@ var Storage = class {
 // package.json
 var package_default = {
   name: "@sendoracloud/sdk-react-native",
-  version: "1.18.0",
+  version: "1.19.0",
   description: "Sendora Cloud React Native + Expo SDK \u2014 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",
@@ -2320,6 +2320,37 @@ var SendoraSDK = class {
   getUserId() {
     return this.userId;
   }
+  /**
+   * Non-throwing, synchronous read of the verified auth principal. Returns
+   * the persisted `AuthUser` (`{ id, email, emailVerified, name, isAnonymous }`)
+   * or `null` when no session is hydrated yet. Zero I/O — a pure in-memory read
+   * of the session restored during `init()` — so it is safe on the very first
+   * API call at cold start: await `init()` once (disk-only, no network), then
+   * read this synchronously, even offline.
+   *
+   * `id` is the JWT `sub` — the durable, server-verified identity to key your
+   * backend data on. Do NOT use `getAnonymousIdSync()` for that (it's a
+   * rotating analytics id). Pair with `isReady()` to tell "still restoring"
+   * apart from "signed out": `null` here while `isReady()` is `false` = init
+   * hasn't finished; `null` while `isReady()` is `true` = genuinely no session.
+   * `isAnonymous` is optional on the wire — test `=== false`, not truthiness.
+   * The access token is re-verified server-side, so reading identity here
+   * (client-untrusted) for UI/routing is safe; never use it as your own
+   * authorization decision.
+   */
+  getUserSync() {
+    return this.ready ? this.auth.getCurrentUser() : null;
+  }
+  /**
+   * Non-throwing, synchronous readiness flag. `true` once `init()` has
+   * resolved (storage hydrated + auth session restored). Gate a cold-start
+   * identity read on this so you never mistake "still restoring the session"
+   * for "signed out" — the loading gate every mobile auth SDK expects
+   * (Firebase's init-null caveat, Clerk's `isLoaded`).
+   */
+  isReady() {
+    return this.ready;
+  }
   /** Toggle consent at runtime — when false, events drop instead of fire. */
   setConsent(granted) {
     this.consentGranted = granted;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sendoracloud/sdk-react-native",
-  "version": "1.18.0",
+  "version": "1.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",