@sendoracloud/sdk-react-native 0.13.0 → 0.14.0

package/dist/index.cjs

@@ -235,21 +235,41 @@ var Auth = class {
       this.resolveReady = res;
     });
   }
-  /** Re-hydrate session from storage. Called by the parent SDK
-   *  during init() after Storage.hydrate() has run. Marks the
-   *  internal ready promise as resolved so queued auth calls
-   *  unblock. */
+  /**
+   * Re-hydrate session from storage. Called by the parent SDK during
+   * init() after Storage.hydrate() has run. Marks the internal ready
+   * promise as resolved so queued auth calls unblock.
+   *
+   * s58.47 — restore the user even when the cached ACCESS token is
+   * missing/expired, as long as USER_KEY + REFRESH_KEY are present.
+   * Pre-s58.47 this required BOTH USER_KEY and TOKEN_KEY, which
+   * caused a cold-start regression: if the access token rotated out
+   * of storage (TTL elapsed, app killed between persists, partial
+   * write, AsyncStorage eviction) the user appeared signed out even
+   * though their refresh chain was still alive in storage. Hosts
+   * then called `signInAnonymously()` on every launch and minted a
+   * fresh anon user, fragmenting analytics across sessions
+   * (Pulse News symptom). With the refresh token present, the next
+   * `getAccessToken()` call will silently refresh + restore a valid
+   * access token without disturbing identity.
+   */
   hydrate() {
     const cachedUser = this.hooks.storage.get(USER_KEY);
     const cachedToken = this.hooks.storage.get(TOKEN_KEY);
+    const cachedRefresh = this.hooks.storage.get(REFRESH_KEY);
     const cachedExpires = this.hooks.storage.get(TOKEN_EXPIRES_KEY);
-    if (cachedUser && cachedToken) {
+    if (cachedUser && (cachedToken || cachedRefresh)) {
       try {
         const parsed = JSON.parse(cachedUser);
         if (typeof parsed.id !== "string" || parsed.id.length === 0) throw new Error("invalid cache");
         this.user = parsed;
-        this.accessToken = cachedToken;
-        this.accessExpiresAt = cachedExpires ? Number(cachedExpires) : 0;
+        if (cachedToken) {
+          this.accessToken = cachedToken;
+          this.accessExpiresAt = cachedExpires ? Number(cachedExpires) : 0;
+        } else {
+          this.accessToken = null;
+          this.accessExpiresAt = 0;
+        }
         this.hooks.onIdentityChange(this.user.id);
       } catch {
         this.hooks.storage.remove(USER_KEY);

package/dist/index.d.cts

@@ -122,10 +122,24 @@ declare class Auth {
     private readyPromise;
     private resolveReady;
     constructor(hooks: AuthHooks);
-    /** Re-hydrate session from storage. Called by the parent SDK
-     *  during init() after Storage.hydrate() has run. Marks the
-     *  internal ready promise as resolved so queued auth calls
-     *  unblock. */
+    /**
+     * Re-hydrate session from storage. Called by the parent SDK during
+     * init() after Storage.hydrate() has run. Marks the internal ready
+     * promise as resolved so queued auth calls unblock.
+     *
+     * s58.47 — restore the user even when the cached ACCESS token is
+     * missing/expired, as long as USER_KEY + REFRESH_KEY are present.
+     * Pre-s58.47 this required BOTH USER_KEY and TOKEN_KEY, which
+     * caused a cold-start regression: if the access token rotated out
+     * of storage (TTL elapsed, app killed between persists, partial
+     * write, AsyncStorage eviction) the user appeared signed out even
+     * though their refresh chain was still alive in storage. Hosts
+     * then called `signInAnonymously()` on every launch and minted a
+     * fresh anon user, fragmenting analytics across sessions
+     * (Pulse News symptom). With the refresh token present, the next
+     * `getAccessToken()` call will silently refresh + restore a valid
+     * access token without disturbing identity.
+     */
     hydrate(): void;
     getCurrentUser(): AuthUser | null;
     /**

package/dist/index.d.ts

@@ -122,10 +122,24 @@ declare class Auth {
     private readyPromise;
     private resolveReady;
     constructor(hooks: AuthHooks);
-    /** Re-hydrate session from storage. Called by the parent SDK
-     *  during init() after Storage.hydrate() has run. Marks the
-     *  internal ready promise as resolved so queued auth calls
-     *  unblock. */
+    /**
+     * Re-hydrate session from storage. Called by the parent SDK during
+     * init() after Storage.hydrate() has run. Marks the internal ready
+     * promise as resolved so queued auth calls unblock.
+     *
+     * s58.47 — restore the user even when the cached ACCESS token is
+     * missing/expired, as long as USER_KEY + REFRESH_KEY are present.
+     * Pre-s58.47 this required BOTH USER_KEY and TOKEN_KEY, which
+     * caused a cold-start regression: if the access token rotated out
+     * of storage (TTL elapsed, app killed between persists, partial
+     * write, AsyncStorage eviction) the user appeared signed out even
+     * though their refresh chain was still alive in storage. Hosts
+     * then called `signInAnonymously()` on every launch and minted a
+     * fresh anon user, fragmenting analytics across sessions
+     * (Pulse News symptom). With the refresh token present, the next
+     * `getAccessToken()` call will silently refresh + restore a valid
+     * access token without disturbing identity.
+     */
     hydrate(): void;
     getCurrentUser(): AuthUser | null;
     /**

package/dist/index.js

@@ -195,21 +195,41 @@ var Auth = class {
       this.resolveReady = res;
     });
   }
-  /** Re-hydrate session from storage. Called by the parent SDK
-   *  during init() after Storage.hydrate() has run. Marks the
-   *  internal ready promise as resolved so queued auth calls
-   *  unblock. */
+  /**
+   * Re-hydrate session from storage. Called by the parent SDK during
+   * init() after Storage.hydrate() has run. Marks the internal ready
+   * promise as resolved so queued auth calls unblock.
+   *
+   * s58.47 — restore the user even when the cached ACCESS token is
+   * missing/expired, as long as USER_KEY + REFRESH_KEY are present.
+   * Pre-s58.47 this required BOTH USER_KEY and TOKEN_KEY, which
+   * caused a cold-start regression: if the access token rotated out
+   * of storage (TTL elapsed, app killed between persists, partial
+   * write, AsyncStorage eviction) the user appeared signed out even
+   * though their refresh chain was still alive in storage. Hosts
+   * then called `signInAnonymously()` on every launch and minted a
+   * fresh anon user, fragmenting analytics across sessions
+   * (Pulse News symptom). With the refresh token present, the next
+   * `getAccessToken()` call will silently refresh + restore a valid
+   * access token without disturbing identity.
+   */
   hydrate() {
     const cachedUser = this.hooks.storage.get(USER_KEY);
     const cachedToken = this.hooks.storage.get(TOKEN_KEY);
+    const cachedRefresh = this.hooks.storage.get(REFRESH_KEY);
     const cachedExpires = this.hooks.storage.get(TOKEN_EXPIRES_KEY);
-    if (cachedUser && cachedToken) {
+    if (cachedUser && (cachedToken || cachedRefresh)) {
       try {
         const parsed = JSON.parse(cachedUser);
         if (typeof parsed.id !== "string" || parsed.id.length === 0) throw new Error("invalid cache");
         this.user = parsed;
-        this.accessToken = cachedToken;
-        this.accessExpiresAt = cachedExpires ? Number(cachedExpires) : 0;
+        if (cachedToken) {
+          this.accessToken = cachedToken;
+          this.accessExpiresAt = cachedExpires ? Number(cachedExpires) : 0;
+        } else {
+          this.accessToken = null;
+          this.accessExpiresAt = 0;
+        }
         this.hooks.onIdentityChange(this.user.id);
       } catch {
         this.hooks.storage.remove(USER_KEY);

package/package.json

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