[bug] Custom wallet group not functioning in the new beta release about rainbowkit

[DanielSinclair]

@SyedAhkam To clarify, the wallet you added is still available, it is just moved to an Installed list at the top, because it is detected as installed by the new EIP-6963 connection standard. This is how Wagmi v2 and other libraries will work going forward, so that dApps won't always need to include wallet connectors; every installed wallet will just appear under Installed. If you add more wallets to your Recommended section in your example, or disable the OKX wallet or visit on mobile, those wallets will continue appear under Recommended.

[DanielSinclair]

@SyedAhkam The missing string will be fixed in 2.0.0-beta.1 shortly.

[magiziz]

@SyedAhkam Yeah we will mention this in the upcoming docs once we merge beta into main branch. It'll be shown in the custom wallet list.

[magiziz]

@SyedAhkam This is an expected behaviour. OKX wallet supports EIP6963. If we detect an EIP6963 wallet we remove that same wallet you specified in the wallet list group.

The reason we do this is because it will be easier for the dApp to connect and manage wallets. There won't be any overridden bugs which usually happens if we don't support EIP6963 overrides.

Regarding the "Installed" missing that's expected. We haven't added localization support for that. It'll be fixed soon 🙏

[SyedAhkam]

@SyedAhkam This is an expected behaviour. OKX wallet supports EIP6963. If we detect an EIP6963 wallet we remove that same wallet you specified in the wallet list group.

The reason we do this is because it will be easier for the dApp to connect and manage wallets. There won't be any overridden bugs which usually happens if we don't support EIP6963 overrides.

I understand the intent. However as it used to work fine in v1, but fails to in v2 -- we could call this a regression.

Now perhaps:

1. You could add a way to override that EIP6963 wallet detection.
2. or IMO The regression / breaking change should be mentioned in the new upcoming docs.