fix: RPC request with id already seen error when using firefox

[ffmcgee725]

When using @metamask/connect in the Firefox Extension, when the dapp side disconnects, the UI updates correctly, but attempting to reconnect does not prompt the wallet pop-up for permission granting.

This happens because createDupeReqFilterStream middleware is responsible for keeping track of IDs that have been recently seen and not respond to request incoming from these matching IDs.

On disconnect, calling getUniqueId function once at the beginning of windowPostMessageTransport was not enough to make sure we avoid repeated IDs, so the proposed fix here is to make sure we call it on each individual request, guaranteeing the unique requests make it through.

• Fixes https://consensyssoftware.atlassian.net/browse/WAPI-873

Screenshots/Recordings

Before

Screen.Recording.2025-12-03.at.11.43.05.mov

After

Screen.Recording.2025-12-04.at.12.37.40.mov

---

Note

Use getUniqueId for every windowPostMessageTransport request to avoid duplicate RPC IDs (Firefox), and document in CHANGELOG.

• Transport
  • src/transports/windowPostMessageTransport.ts: Generate a new id via getUniqueId() for each request, replacing the incremented counter to prevent duplicate RPC IDs.
• Docs
  • CHANGELOG.md: Add Unreleased entry under Fixed describing the per-request getUniqueId change and associated Firefox duplicate ID issue.

^{Written by Cursor Bugbot for commit d1b49ef. This will update automatically on new commits. Configure here.}

[wenfix]

LGTM 🔥