You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
@metamask/connect-evm 2.1.1
Added
Resolve wallet_getCapabilities locally from the cached session when possible, avoiding a deeplink round-trip (#339)
Fixed
Recognize MetaMask Flask (io.metamask.flask) as a native MetaMask EIP-6963 provider. The MMConnect-managed provider announcement is now suppressed when Flask has announced, avoiding a duplicate MetaMask entry in wallet pickers. (#336)
@metamask/connect-multichain 1.2.0
Added
Resolve wallet_getCapabilities locally from the cached session on the MWP (mobile deeplink) transport, avoiding a deeplink round-trip. When the wallet publishes EIP-5792 capabilities in sessionProperties.eip155Capabilities, RequestRouter answers wallet_getCapabilities from the transport's cached session (read cache-only via the new getCachedSession accessor, so a cache miss falls back to the deeplink immediately; case-insensitive address/chain lookup) and falls back to the wallet on any miss, partial chain coverage, malformed params, or an older wallet that doesn't publish capabilities. (#339)
Add optional getCachedSession to the exported ExtendedTransport type: a cache-only read of the stored wallet_getSession result that resolves undefined on a miss instead of issuing a live request (and never replays transport notifications). Implemented by the MWP transport; transports without a session cache simply omit it. (#339)
Fixed
Recognize MetaMask Flask (io.metamask.flask) as a native MetaMask extension in EIP-6963 detection. hasExtension() now returns true when only Flask is installed, so connect() uses the browser extension transport instead of falling back to the MWP/QR flow. (#336)
Closing the QR code / install modal mid-connection now emits mmconnect_connection_rejected instead of mmconnect_connection_failed. Modal close is a user-driven cancellation; it previously rejected with a plain Error('User closed modal') that isRejectionError did not recognise, so user cancellations polluted the _failed bucket. The close handler now rejects with the canonical EIP-1193 4001 error (providerErrors.userRejectedRequest()). Genuine errors (transport timeouts/disconnects, wallet RPC errors) still emit mmconnect_connection_failed. (#333)
@metamask/connect-solana 2.1.1
Changed
Bump @metamask/connect-multichain to ^1.2.0 (#340)
@metamask/browser-playground 0.8.2
Added
Add a wallet_getCapabilities button to the Legacy EVM card's read-only RPC calls, requesting EIP-5792 capabilities for the active account (scoped to the connected chain when available). (#339)
