@sendoracloud/sdk-react-native 0.10.1 → 0.10.3

package/dist/index.cjs

@@ -231,9 +231,14 @@ var Auth = class {
     this.inflight = Promise.resolve();
     this.refreshInflight = null;
     this.hooks = hooks;
+    this.readyPromise = new Promise((res) => {
+      this.resolveReady = res;
+    });
   }
   /** Re-hydrate session from storage. Called by the parent SDK
-   *  during init() after Storage.hydrate() has run. */
+   *  during init() after Storage.hydrate() has run. Marks the
+   *  internal ready promise as resolved so queued auth calls
+   *  unblock. */
   hydrate() {
     const cachedUser = this.hooks.storage.get(USER_KEY);
     const cachedToken = this.hooks.storage.get(TOKEN_KEY);
@@ -253,6 +258,7 @@ var Auth = class {
         this.hooks.storage.remove(REFRESH_KEY);
       }
     }
+    this.resolveReady();
   }
   getCurrentUser() {
     return this.user;
@@ -283,11 +289,29 @@ var Auth = class {
       return data.user;
     });
   }
+  /**
+   * Create an email/password account.
+   *
+   * Industry-standard upgrade-first flow (matches Firebase
+   * `linkWithCredential`, Auth0 anonymous-merge, Supabase
+   * `linkIdentity`): when a refresh token is present in storage we
+   * try `/auth-service/upgrade` first — backend validates the
+   * refresh, checks the bound user is anonymous, and promotes in
+   * place preserving `user.id`. If the bound user is NOT anonymous
+   * (already identified, expired refresh, etc.), backend rejects
+   * with FORBIDDEN_NON_ANONYMOUS / INVALID_REFRESH and we fall back
+   * to a fresh /signup.
+   *
+   * Why we don't gate on the cached `this.user.isAnonymous`
+   * boolean: the in-memory user can be stale during cold start or
+   * fast-refresh races. The refresh token in storage is the
+   * authoritative signal — if it's there, the upgrade path is
+   * worth attempting; backend has the source of truth.
+   */
   signUp(email, password, opts) {
     return this.serialize(async () => {
       const refresh = this.hooks.storage.get(REFRESH_KEY);
-      const isAnonymous = this.user?.isAnonymous === true;
-      if (isAnonymous && refresh) {
+      if (refresh) {
         try {
           const data = await this.callAuth("/api/v1/auth-service/upgrade", {
             refreshToken: refresh,
@@ -301,11 +325,13 @@ var Auth = class {
           if (err instanceof AuthError && (err.code === "CONFLICT" || err.code === "EMAIL_ALREADY_TAKEN")) {
             throw new EmailAlreadyTakenError(err.message);
           }
-          throw err;
+          if (err instanceof AuthError && (err.code === "FORBIDDEN_NON_ANONYMOUS" || err.code === "INVALID_REFRESH" || err.code === "UNAUTHORIZED" || err.code === "REFRESH_EXPIRED")) {
+            await this.wipeLocalIdentity();
+          } else {
+            throw err;
+          }
         }
       }
-      const wasIdentified = this.user !== null && this.user.isAnonymous === false;
-      if (wasIdentified) await this.wipeLocalIdentity();
       try {
         const data = await this.callAuth("/api/v1/auth-service/signup", {
           email,
@@ -685,7 +711,11 @@ var Auth = class {
   }
   // --- internals ---
   serialize(op) {
-    const next = this.inflight.then(op, op);
+    const guarded = async () => {
+      await this.readyPromise;
+      return op();
+    };
+    const next = this.inflight.then(guarded, guarded);
     this.inflight = next.catch(() => void 0);
     return next;
   }
@@ -770,7 +800,7 @@ function decodeJwtPayload(token) {
 }
 
 // src/index.ts
-var SDK_VERSION = "0.10.1";
+var SDK_VERSION = "0.10.3";
 var DEFAULT_API_URL = "https://api.sendoracloud.com";
 var ANON_KEY = "anon_id";
 var USER_ID_KEY = "user_id";

package/dist/index.d.cts

@@ -106,9 +106,26 @@ declare class Auth {
     private accessExpiresAt;
     private inflight;
     private refreshInflight;
+    /**
+     * Resolves when the parent SDK has finished its async init() —
+     * AsyncStorage hydrated + auth.hydrate() restored the cached
+     * session. All public auth methods await this internally so a
+     * customer who forgets `await sendora.init()` before showing the
+     * signup UI doesn't hit the cold-start race where the upgrade
+     * path's `storage.get(REFRESH_KEY)` returns null even though a
+     * valid anonymous session is sitting on disk.
+     *
+     * Industry-standard "SDK gates on internal readiness" pattern
+     * (Firebase Auth, Auth0, Clerk all do equivalent internal
+     * gating).
+     */
+    private readyPromise;
+    private resolveReady;
     constructor(hooks: AuthHooks);
     /** Re-hydrate session from storage. Called by the parent SDK
-     *  during init() after Storage.hydrate() has run. */
+     *  during init() after Storage.hydrate() has run. Marks the
+     *  internal ready promise as resolved so queued auth calls
+     *  unblock. */
     hydrate(): void;
     getCurrentUser(): AuthUser | null;
     /**
@@ -123,6 +140,25 @@ declare class Auth {
         name?: string;
         metadata?: Record<string, unknown>;
     }): Promise<AuthUser>;
+    /**
+     * Create an email/password account.
+     *
+     * Industry-standard upgrade-first flow (matches Firebase
+     * `linkWithCredential`, Auth0 anonymous-merge, Supabase
+     * `linkIdentity`): when a refresh token is present in storage we
+     * try `/auth-service/upgrade` first — backend validates the
+     * refresh, checks the bound user is anonymous, and promotes in
+     * place preserving `user.id`. If the bound user is NOT anonymous
+     * (already identified, expired refresh, etc.), backend rejects
+     * with FORBIDDEN_NON_ANONYMOUS / INVALID_REFRESH and we fall back
+     * to a fresh /signup.
+     *
+     * Why we don't gate on the cached `this.user.isAnonymous`
+     * boolean: the in-memory user can be stale during cold start or
+     * fast-refresh races. The refresh token in storage is the
+     * authoritative signal — if it's there, the upgrade path is
+     * worth attempting; backend has the source of truth.
+     */
     signUp(email: string, password: string, opts?: {
         name?: string;
         metadata?: Record<string, unknown>;

package/dist/index.d.ts

@@ -106,9 +106,26 @@ declare class Auth {
     private accessExpiresAt;
     private inflight;
     private refreshInflight;
+    /**
+     * Resolves when the parent SDK has finished its async init() —
+     * AsyncStorage hydrated + auth.hydrate() restored the cached
+     * session. All public auth methods await this internally so a
+     * customer who forgets `await sendora.init()` before showing the
+     * signup UI doesn't hit the cold-start race where the upgrade
+     * path's `storage.get(REFRESH_KEY)` returns null even though a
+     * valid anonymous session is sitting on disk.
+     *
+     * Industry-standard "SDK gates on internal readiness" pattern
+     * (Firebase Auth, Auth0, Clerk all do equivalent internal
+     * gating).
+     */
+    private readyPromise;
+    private resolveReady;
     constructor(hooks: AuthHooks);
     /** Re-hydrate session from storage. Called by the parent SDK
-     *  during init() after Storage.hydrate() has run. */
+     *  during init() after Storage.hydrate() has run. Marks the
+     *  internal ready promise as resolved so queued auth calls
+     *  unblock. */
     hydrate(): void;
     getCurrentUser(): AuthUser | null;
     /**
@@ -123,6 +140,25 @@ declare class Auth {
         name?: string;
         metadata?: Record<string, unknown>;
     }): Promise<AuthUser>;
+    /**
+     * Create an email/password account.
+     *
+     * Industry-standard upgrade-first flow (matches Firebase
+     * `linkWithCredential`, Auth0 anonymous-merge, Supabase
+     * `linkIdentity`): when a refresh token is present in storage we
+     * try `/auth-service/upgrade` first — backend validates the
+     * refresh, checks the bound user is anonymous, and promotes in
+     * place preserving `user.id`. If the bound user is NOT anonymous
+     * (already identified, expired refresh, etc.), backend rejects
+     * with FORBIDDEN_NON_ANONYMOUS / INVALID_REFRESH and we fall back
+     * to a fresh /signup.
+     *
+     * Why we don't gate on the cached `this.user.isAnonymous`
+     * boolean: the in-memory user can be stale during cold start or
+     * fast-refresh races. The refresh token in storage is the
+     * authoritative signal — if it's there, the upgrade path is
+     * worth attempting; backend has the source of truth.
+     */
     signUp(email: string, password: string, opts?: {
         name?: string;
         metadata?: Record<string, unknown>;

package/dist/index.js

@@ -191,9 +191,14 @@ var Auth = class {
     this.inflight = Promise.resolve();
     this.refreshInflight = null;
     this.hooks = hooks;
+    this.readyPromise = new Promise((res) => {
+      this.resolveReady = res;
+    });
   }
   /** Re-hydrate session from storage. Called by the parent SDK
-   *  during init() after Storage.hydrate() has run. */
+   *  during init() after Storage.hydrate() has run. Marks the
+   *  internal ready promise as resolved so queued auth calls
+   *  unblock. */
   hydrate() {
     const cachedUser = this.hooks.storage.get(USER_KEY);
     const cachedToken = this.hooks.storage.get(TOKEN_KEY);
@@ -213,6 +218,7 @@ var Auth = class {
         this.hooks.storage.remove(REFRESH_KEY);
       }
     }
+    this.resolveReady();
   }
   getCurrentUser() {
     return this.user;
@@ -243,11 +249,29 @@ var Auth = class {
       return data.user;
     });
   }
+  /**
+   * Create an email/password account.
+   *
+   * Industry-standard upgrade-first flow (matches Firebase
+   * `linkWithCredential`, Auth0 anonymous-merge, Supabase
+   * `linkIdentity`): when a refresh token is present in storage we
+   * try `/auth-service/upgrade` first — backend validates the
+   * refresh, checks the bound user is anonymous, and promotes in
+   * place preserving `user.id`. If the bound user is NOT anonymous
+   * (already identified, expired refresh, etc.), backend rejects
+   * with FORBIDDEN_NON_ANONYMOUS / INVALID_REFRESH and we fall back
+   * to a fresh /signup.
+   *
+   * Why we don't gate on the cached `this.user.isAnonymous`
+   * boolean: the in-memory user can be stale during cold start or
+   * fast-refresh races. The refresh token in storage is the
+   * authoritative signal — if it's there, the upgrade path is
+   * worth attempting; backend has the source of truth.
+   */
   signUp(email, password, opts) {
     return this.serialize(async () => {
       const refresh = this.hooks.storage.get(REFRESH_KEY);
-      const isAnonymous = this.user?.isAnonymous === true;
-      if (isAnonymous && refresh) {
+      if (refresh) {
         try {
           const data = await this.callAuth("/api/v1/auth-service/upgrade", {
             refreshToken: refresh,
@@ -261,11 +285,13 @@ var Auth = class {
           if (err instanceof AuthError && (err.code === "CONFLICT" || err.code === "EMAIL_ALREADY_TAKEN")) {
             throw new EmailAlreadyTakenError(err.message);
           }
-          throw err;
+          if (err instanceof AuthError && (err.code === "FORBIDDEN_NON_ANONYMOUS" || err.code === "INVALID_REFRESH" || err.code === "UNAUTHORIZED" || err.code === "REFRESH_EXPIRED")) {
+            await this.wipeLocalIdentity();
+          } else {
+            throw err;
+          }
         }
       }
-      const wasIdentified = this.user !== null && this.user.isAnonymous === false;
-      if (wasIdentified) await this.wipeLocalIdentity();
       try {
         const data = await this.callAuth("/api/v1/auth-service/signup", {
           email,
@@ -645,7 +671,11 @@ var Auth = class {
   }
   // --- internals ---
   serialize(op) {
-    const next = this.inflight.then(op, op);
+    const guarded = async () => {
+      await this.readyPromise;
+      return op();
+    };
+    const next = this.inflight.then(guarded, guarded);
     this.inflight = next.catch(() => void 0);
     return next;
   }
@@ -730,7 +760,7 @@ function decodeJwtPayload(token) {
 }
 
 // src/index.ts
-var SDK_VERSION = "0.10.1";
+var SDK_VERSION = "0.10.3";
 var DEFAULT_API_URL = "https://api.sendoracloud.com";
 var ANON_KEY = "anon_id";
 var USER_ID_KEY = "user_id";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sendoracloud/sdk-react-native",
-  "version": "0.10.1",
+  "version": "0.10.3",
   "description": "Sendora Cloud React Native + Expo SDK — analytics, identity, push-token registration, auth. Expo Go compatible, no native modules beyond AsyncStorage.",
   "type": "module",
   "main": "./dist/index.cjs",