@synclib-io/sync 0.2.1 → 0.2.2

package/dist/index.d.mts

@@ -552,6 +552,24 @@ declare class SyncClient {
     private serverHashColumns?;
     private isInitialized;
     private hasConnectedOnce;
+    /**
+     * True while a call to [connect] is in progress. Used by
+     * [handleStateChange] to skip its auto-rejoin of channels when an
+     * explicit caller is already going to call [joinChannels] itself.
+     *
+     * Without this guard, every reconnect after the first one races two
+     * `joinChannels()` invocations against each other: one from `connect()`'s
+     * `await this.joinChannels()` and one from `handleStateChange`'s fire-and-
+     * forget call. `WebSocketManager.joinChannel` (line 192-196) EVICTS any
+     * existing channel for the same topic before creating a new one, so the
+     * second call disposes the first call's channel — its push completer
+     * never sees the reply, the await hangs until the phoenix-js push
+     * timeout fires. Symptom server-side: two `JOINED <topic>` events ~50ms
+     * apart with the same device_id; client-side: 30s wait then timeout
+     * even though the channel is functionally joined via the surviving
+     * second call. Mirror of the Dart fix in synclib_sync/sync_client.dart.
+     */
+    private explicitConnectInProgress;
     /**
      * Per-install identifier minted on first DB open and persisted in
      * `_synclib_metadata`. Stable for the life of the SQLite/IndexedDB file.

package/dist/index.d.ts

@@ -552,6 +552,24 @@ declare class SyncClient {
     private serverHashColumns?;
     private isInitialized;
     private hasConnectedOnce;
+    /**
+     * True while a call to [connect] is in progress. Used by
+     * [handleStateChange] to skip its auto-rejoin of channels when an
+     * explicit caller is already going to call [joinChannels] itself.
+     *
+     * Without this guard, every reconnect after the first one races two
+     * `joinChannels()` invocations against each other: one from `connect()`'s
+     * `await this.joinChannels()` and one from `handleStateChange`'s fire-and-
+     * forget call. `WebSocketManager.joinChannel` (line 192-196) EVICTS any
+     * existing channel for the same topic before creating a new one, so the
+     * second call disposes the first call's channel — its push completer
+     * never sees the reply, the await hangs until the phoenix-js push
+     * timeout fires. Symptom server-side: two `JOINED <topic>` events ~50ms
+     * apart with the same device_id; client-side: 30s wait then timeout
+     * even though the channel is functionally joined via the surviving
+     * second call. Mirror of the Dart fix in synclib_sync/sync_client.dart.
+     */
+    private explicitConnectInProgress;
     /**
      * Per-install identifier minted on first DB open and persisted in
      * `_synclib_metadata`. Stable for the life of the SQLite/IndexedDB file.

package/dist/index.js

@@ -922,6 +922,24 @@ var SyncClient = class {
   constructor(config) {
     this.isInitialized = false;
     this.hasConnectedOnce = false;
+    /**
+     * True while a call to [connect] is in progress. Used by
+     * [handleStateChange] to skip its auto-rejoin of channels when an
+     * explicit caller is already going to call [joinChannels] itself.
+     *
+     * Without this guard, every reconnect after the first one races two
+     * `joinChannels()` invocations against each other: one from `connect()`'s
+     * `await this.joinChannels()` and one from `handleStateChange`'s fire-and-
+     * forget call. `WebSocketManager.joinChannel` (line 192-196) EVICTS any
+     * existing channel for the same topic before creating a new one, so the
+     * second call disposes the first call's channel — its push completer
+     * never sees the reply, the await hangs until the phoenix-js push
+     * timeout fires. Symptom server-side: two `JOINED <topic>` events ~50ms
+     * apart with the same device_id; client-side: 30s wait then timeout
+     * even though the channel is functionally joined via the surviving
+     * second call. Mirror of the Dart fix in synclib_sync/sync_client.dart.
+     */
+    this.explicitConnectInProgress = false;
     /**
      * Per-install identifier minted on first DB open and persisted in
      * `_synclib_metadata`. Stable for the life of the SQLite/IndexedDB file.
@@ -1114,12 +1132,17 @@ var SyncClient = class {
     if (!this.isInitialized) {
       throw new Error("Not initialized. Call initialize() first.");
     }
-    await this.ws.connect({
-      token,
-      client_id: this.config.clientId,
-      ...extra || {}
-    });
-    await this.joinChannels();
+    this.explicitConnectInProgress = true;
+    try {
+      await this.ws.connect({
+        token,
+        client_id: this.config.clientId,
+        ...extra || {}
+      });
+      await this.joinChannels();
+    } finally {
+      this.explicitConnectInProgress = false;
+    }
   }
   /**
    * Update the auth token used on subsequent (re)connects without tearing
@@ -2114,7 +2137,7 @@ var SyncClient = class {
         this.updateSyncState("error" /* ERROR */);
         break;
     }
-    if (state === "connected" /* CONNECTED */ && this.hasConnectedOnce) {
+    if (state === "connected" /* CONNECTED */ && this.hasConnectedOnce && !this.explicitConnectInProgress) {
       console.log("Reconnected - rejoining channels");
       this.joinChannels().catch((e) => {
         console.error("Failed to rejoin channels after reconnect:", e);

package/dist/index.mjs

@@ -889,6 +889,24 @@ var SyncClient = class {
   constructor(config) {
     this.isInitialized = false;
     this.hasConnectedOnce = false;
+    /**
+     * True while a call to [connect] is in progress. Used by
+     * [handleStateChange] to skip its auto-rejoin of channels when an
+     * explicit caller is already going to call [joinChannels] itself.
+     *
+     * Without this guard, every reconnect after the first one races two
+     * `joinChannels()` invocations against each other: one from `connect()`'s
+     * `await this.joinChannels()` and one from `handleStateChange`'s fire-and-
+     * forget call. `WebSocketManager.joinChannel` (line 192-196) EVICTS any
+     * existing channel for the same topic before creating a new one, so the
+     * second call disposes the first call's channel — its push completer
+     * never sees the reply, the await hangs until the phoenix-js push
+     * timeout fires. Symptom server-side: two `JOINED <topic>` events ~50ms
+     * apart with the same device_id; client-side: 30s wait then timeout
+     * even though the channel is functionally joined via the surviving
+     * second call. Mirror of the Dart fix in synclib_sync/sync_client.dart.
+     */
+    this.explicitConnectInProgress = false;
     /**
      * Per-install identifier minted on first DB open and persisted in
      * `_synclib_metadata`. Stable for the life of the SQLite/IndexedDB file.
@@ -1081,12 +1099,17 @@ var SyncClient = class {
     if (!this.isInitialized) {
       throw new Error("Not initialized. Call initialize() first.");
     }
-    await this.ws.connect({
-      token,
-      client_id: this.config.clientId,
-      ...extra || {}
-    });
-    await this.joinChannels();
+    this.explicitConnectInProgress = true;
+    try {
+      await this.ws.connect({
+        token,
+        client_id: this.config.clientId,
+        ...extra || {}
+      });
+      await this.joinChannels();
+    } finally {
+      this.explicitConnectInProgress = false;
+    }
   }
   /**
    * Update the auth token used on subsequent (re)connects without tearing
@@ -2081,7 +2104,7 @@ var SyncClient = class {
         this.updateSyncState("error" /* ERROR */);
         break;
     }
-    if (state === "connected" /* CONNECTED */ && this.hasConnectedOnce) {
+    if (state === "connected" /* CONNECTED */ && this.hasConnectedOnce && !this.explicitConnectInProgress) {
       console.log("Reconnected - rejoining channels");
       this.joinChannels().catch((e) => {
         console.error("Failed to rejoin channels after reconnect:", e);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@synclib-io/sync",
-  "version": "0.2.1",
+  "version": "0.2.2",
   "description": "TypeScript/JavaScript sync client for coordinating database changes with Elixir Phoenix server",
   "publishConfig": {
     "access": "public"