hailin
b231667aba
When switching message/event streams, the old stream's 'end' or 'error' events could fire after the new stream was created. Since activeMessageSubscription was already updated to the new session, the old stream's events would incorrectly trigger reconnection, causing TSS message routing to fail. Fix: - Remove event listeners from old stream before canceling - Use closure to capture current stream reference - Check if event is from current active stream before triggering reconnect This fixes the "Not connected" error during co-sign TSS message routing. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| account-client.ts | ||
| address-derivation.ts | ||
| database.ts | ||
| grpc-client.ts | ||
| kava-client.ts | ||
| kava-tx-service.ts | ||
| storage.ts | ||
| tss-handler.ts | ||