Appearance

Releases ​

The release notes for our @privy-io/wagmi-connector SDK.

INFO

Privy has migrated to the @privy-io/wagmi package for wagmi versions 2.x and above.

0.1.12 ​

  • Improve error message string for when new active wallet's network cannot be switched to that of previous active wallet

0.1.11 ​

  • Improve synchronization of wagmi hooks with active wallet state

0.1.10 ​

  • Improve default setting of the activeWallet to be the most recently connected

0.1.9 ​

  • Fix issues with ChainNotConfigured on wagmi calls

0.1.8 ​

  • Require a minimum wagmi version of 1.4.12, which removes the LedgerConnector due to a security vulnerability. Read more here.

0.1.7 ​

  • When setActiveWallet is called, no longer throw an error if the network of the new active wallet cannot be switched to the network of the previous active wallet
  • Allow developers to pass no parameters to Privy's re-exported useSwitchNetwork to be at parity with the default wagmi interface
  • Ensure active wallet is always cleared if no wallets are connected
  • Fix issue where active wallet can occasionally refer to a stale connection

0.1.6 ​

  • Fix autoconnect issues with injected wallets
  • Fix temporary disconnection of MetaMask during network switch

0.1.5 ​

  • Expose patched useSwitchNetwork hook
  • Expose privyConnectorOverride prop on PrivyWagmiConnector to support third-party integrations (e.g. ZeroDev)
  • Remove warning around the now deprecated additionalChains property of `PrivyProvider

0.1.4 ​

  • Enable compatibility with the PrivyProvider's additionalChains configuration

0.1.3 ​

  • Ensure wallet client is refetched after active wallet gets updated

0.1.2 ​

  • Fix bug around supported networks. All of react-auth's supported networks should now be supported by wagmi-connector.

0.1.1 ​

  • Fix bug where wagmi's useWalletClient returns an outdated active wallet

0.1.0 ​

  • Enable support for wagmi versions 1.x.x, instead of 0.x.x