Skip to content

fix: transaction subscribe source on websocket reconnect - #1179

Open
venimus wants to merge 1 commit into
developfrom
fix/websocket-tx-subscribe-source-on-reconnect
Open

venimus wants to merge 1 commit into
developfrom
fix/websocket-tx-subscribe-source-on-reconnect

Conversation

@venimus

@venimus venimus commented Sep 8, 2026

Copy link
Copy Markdown
Member

Description

useWebSocket's reconnect handler (openWebSocket()) re-subscribes to a
transaction hash using source: "node", but the live watcher for the same
subscription (watch(subscribedTransactionId, ...)) uses source: "mdw".
Only source: "mdw" supports subscribing to an arbitrary tx hash payload —
source: "node" only handles the KeyBlocks/MicroBlocks channel names.

So after any websocket reconnect (network blip, backend restart) while a user
is on a transaction detail page, the re-subscription silently goes nowhere —
that transaction's live confirmation update never fires again until a full
page reload.

Demo

No visual change — this only affects a background websocket subscribe
message sent after reconnect.

Checklist:

  • I have read and followed the Contributing Guide
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

@github-actions

github-actions Bot commented Sep 8, 2026

Copy link
Copy Markdown

🧪️ Preview Links 🔎️

Mainnet: https://pr-1179-aescan.stg.service.aepps.com
Testnet: https://pr-1179-aescan-testnet.stg.service.aepps.com

This branch has not been deployed

No deployments
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