Skip to content

fix(cli-sdk): fix swidge session mismatch and relay error crash#40

Merged
arein merged 1 commit into
mainfrom
fix/swidge-session-and-relay-errors
Mar 9, 2026
Merged

fix(cli-sdk): fix swidge session mismatch and relay error crash#40
arein merged 1 commit into
mainfrom
fix/swidge-session-and-relay-errors

Conversation

@arein
Copy link
Copy Markdown
Contributor

@arein arein commented Mar 9, 2026

Summary

  • Swidge NO_MATCHING_KEY fix: Only include fromChain in session namespaces — the bridge tx is sent on the source chain, so including toChain caused NO_MATCHING_KEY when restoring sessions that didn't have the destination chain approved
  • Relay error crash fix: Capture relay WebSocket errors during request() so wallet rejection/timeout doesn't crash Node with an unhandled 'error' event (matches existing pattern in disconnect())

Test plan

  • npm run build — all packages build
  • npm run test — all 107 tests pass
  • Manual: run walletconnect swidge with a cross-chain bridge, verify session restore works
  • Manual: reject a signing request in wallet, verify clean error message instead of crash

🤖 Generated with Claude Code

…ay errors

1. Only include fromChain in session namespaces — bridge tx is sent on
   the source chain, so including toChain caused NO_MATCHING_KEY when
   restoring sessions without the destination chain approved.

2. Capture relay errors during request() so wallet rejection/timeout
   doesn't crash Node with an unhandled 'error' event.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@arein arein merged commit 88b7bea into main Mar 9, 2026
4 checks passed
@github-actions github-actions Bot mentioned this pull request Mar 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant