fix(wallets): connect Brave Wallet on mobile without a second tap

[jackkru69]

Summary

Fixes Brave Wallet connections on mobile browsers requiring a second tap in RainbowKit’s connect modal.

Problem

Wagmi’s injected connector uses wallet_requestPermissions when shimDisconnect is enabled. On Brave mobile, the permission response may not include account addresses in caveats, causing Wagmi to fall back to eth_requestAccounts.

While the native permissions dialog is still closing, that second request can fail with -32002 (“Already processing request”), leaving the modal open until the user taps the connector again.

Solution

• Keep Wagmi’s default shimDisconnect behavior, so an explicit disconnect remains persisted across reloads.
• On mobile Brave only, adapt the connection handshake so wallet_requestPermissions is fulfilled through one direct eth_requestAccounts request and returns a Wagmi-compatible permission response.
• Scope the adapter strictly to connector.connect(). After connecting, connector.getProvider() resolves to the original Brave provider, so application-initiated wallet_requestPermissions calls and their caveats are forwarded unchanged.
• Add unit coverage for:
  • first-tap mobile connection;
  • desktop default permissions behavior;
  • persisted disconnect state;
  • forwarding post-connect permission requests unchanged.

Testing

• pnpm test
• pnpm --filter @rainbow-me/rainbowkit typecheck
• formatting and diff checks

[changeset-bot]

🦋 Changeset detected

Latest commit: 5f3eaf6

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 18 packages

Name	Type
@rainbow-me/rainbowkit	Patch
example	Patch
@rainbow-me/rainbow-button	Patch
rainbowkit-next-app	Patch
site	Patch
with-create-react-app	Patch
with-next-app-i18n	Patch
with-next-app	Patch
with-next-custom-button	Patch
with-next-mint-nft	Patch
with-next-siwe-iron-session	Patch
with-next-siwe-next-auth	Patch
with-next-wallet-button	Patch
with-next	Patch
with-react-router	Patch
with-remix	Patch
with-vite	Patch
with-next-rainbow-button	Patch

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

[vercel]

@jackkru69 is attempting to deploy a commit to the rainbowdotme Team on Vercel.

A member of the Team first needs to authorize it.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 05fd323d1d

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b173172e4c

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".