diff options
| author | Christophe Besson <cbesson@gmail.com> | 2026-08-26 13:54:56 +0200 |
|---|---|---|
| committer | Christophe Besson <cbesson@gmail.com> | 2026-08-26 13:54:56 +0200 |
| commit | a31b26df45860af16061fb43ccc3443381ed3df2 (patch) | |
| tree | dc46e6d6b8efa6d5c23ec4af255072f96458f72b /packages/meshbay-hub/src/meshbay_hub/static/group-page.js | |
| parent | 5ebebb8748453323709136d86f3b027cee309d4d (diff) | |
| download | meshbay-a31b26df45860af16061fb43ccc3443381ed3df2.tar.gz | |
fix(transport): reconnect used a fresh handshake token but a stale signaling one
Found live: every reconnect attempt failed "Signaling failed: 401 Invalid
or expired token", looping for 4+ minutes with no chance of ever
succeeding. connect() takes one token but uses it in two places — the
handshake sent to the node, and the Authorization header on the signaling
POST to the hub — and only the constructor's original `this._accessToken`
was ever used for the latter. onNeedToken correctly fetches a fresh token
for each reconnect attempt, but it only ever reached the handshake; the
signaling call kept sending whatever token the transport was constructed
with, no matter how many minutes had passed or how many attempts fetched
a new one.
connect() now updates this._accessToken on every call, reconnects included,
so both places use the same current token.
Diffstat (limited to 'packages/meshbay-hub/src/meshbay_hub/static/group-page.js')
0 files changed, 0 insertions, 0 deletions