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
When configuring an injected connector according to the docs: https://docs.family.co/connectkit/wallets#configure-wallets-example to modify the list of suggested wallets, a duplicate entry appears in the modal if the wallet’s browser extension (e.g., Bitget Wallet) is detected. This duplication does not occur when the extension is not present.
Open the ConnectKit modal with the Bitget Wallet browser extension installed and enabled.
Expected behavior
Only one entry per wallet should appear in the ConnectKit modal, even if a browser extension for that wallet is detected.
Screenshots
When the Bitget Wallet extension is enabled:
When the extension is disabled:
Environment details
ConnectKit version: 1.8.2
Browser: Chromium Version 130.0.6723.116 (Official Build) Arch Linux (64-bit)
OS: 5.15.167-1-MANJARO
Additional context
After reviewing the wagmi configuration options, there doesn’t appear to be a straightforward way to filter connectors to ensure a single button per wallet instance in the modal.
The text was updated successfully, but these errors were encountered:
Describe the bug
When configuring an injected connector according to the docs: https://docs.family.co/connectkit/wallets#configure-wallets-example to modify the list of suggested wallets, a duplicate entry appears in the modal if the wallet’s browser extension (e.g., Bitget Wallet) is detected. This duplication does not occur when the extension is not present.
To reproduce
Code Example:
Steps to Reproduce:
wagmiConfig
.Expected behavior
Only one entry per wallet should appear in the ConnectKit modal, even if a browser extension for that wallet is detected.
Screenshots
When the Bitget Wallet extension is enabled:
When the extension is disabled:
Environment details
Additional context
After reviewing the wagmi configuration options, there doesn’t appear to be a straightforward way to filter connectors to ensure a single button per wallet instance in the modal.
The text was updated successfully, but these errors were encountered: