fix(siwx): preserve signing context in multichain wallet sessions - #5736
Conversation
🦋 Changeset detectedLatest commit: ef376ce The changes in this PR will be included in the next version bump. This PR includes changesets to release 27 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
9 Skipped Deployments
|
Visual Regression Test Results ✅ PassedChromatic Build: https://www.chromatic.com/build?appId=6493191bf4b10fed8ca7353f&number=1030 👉 Please review the visual changes in Chromatic and accept or reject them. |
📦 Bundle Size Check✅ All bundles are within size limits 📊 View detailed bundle sizes> @reown/appkit-monorepo@1.7.1 size /home/runner/work/appkit/appkit > size-limit |
6b332d1 to
6de1ca6
Compare
ff5a607 to
99da4f4
Compare
Pass caipNetworkId explicitly to UniversalProvider.request() for WalletConnect connections to ensure correct chain context is used, fixing SIWX signing failures with multichain wallets (Trust, SafePal).
1830cb8 to
2834963
Compare
|
Approved, do we need to fix this on ethers level as well? |
Nope since we don't set |
Summary
namespacechanges between message creation and signingDefaultSignernow calls adapter directly using captured chainId