Fix useAppKitProvider: Don't wrap walletProvider with ref

[dima74]

Description

Currently walletProvider is wrapped with ref in useAppKitProvider. This creates Proxy for walletProvider, which could result in error like this on some wallets (e.g. MetaMask + Solana) when passing resulting walletProvider as argument to AnchorProvider (solana primary framework):

index-CCid8-zN.js:17 TypeError: Cannot read private member from an object whose class did not declare it
at G (inpage.js:2:131052)
at get accounts (inpage.js:2:255980)
at Reflect.get (<anonymous>)
at MutableReactiveHandler.get (index-CCid8-zN.js:10:11881)
at Proxy.getAccount (index-CCid8-zN.js:1032:4974)
at get publicKey (index-CCid8-zN.js:1032:2238)
at Reflect.get (<anonymous>)
at MutableReactiveHandler.get (index-CCid8-zN.js:10:11881)
at new AnchorProvider (index-CCid8-zN.js:1033:1295)
...

Type of change

• Chore (non-breaking change that addresses non-functional tasks, maintenance, or code quality improvements)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

• Code in this PR is covered by automated tests (Unit tests, E2E tests)
• My changes generate no new warnings
• I have reviewed my own code
• I have filled out all required sections
• I have tested my changes on the preview link
• Approver of this PR confirms that the changes are tested on the preview link

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9c790cc

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

@dima74 is attempting to deploy a commit to the Reown Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

All contributors have signed the CTA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[dima74]

I have read the CTA Document and I hereby sign the CTA

[Copilot]

Pull request overview

This PR fixes a bug in the Vue implementation where wrapping walletProvider with Vue's ref created deep reactive Proxies that caused errors with certain wallets (e.g., MetaMask + Solana) when interfacing with the Solana Anchor framework.

• Changed ref to shallowRef for provider objects to prevent deep reactivity
• Maintained reactivity for subscription updates while avoiding Proxy-related errors

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[0xmkh]

Can you describe a case where ref caused an issue/problem just so i can reproduce the issue on my end?

[dima74]

Created demo: https://stackblitz.com/edit/github-j6in4egw?file=src%2Fcomponents%2Fdemo.ts

Open the project, connect metamask, observe TypeError: Cannot read private member from an object whose class did not declare it exception in browser logs

[glitch-txs]

this is most probably because Anchor is expecting a different interface, you will probably need to build an adapter

[dima74]

this is most probably because Anchor is expecting a different interface, you will probably need to build an adapter

Problem is with ref/reactive wrapping. Without wrapping (e.g. using shallowRef as proposed in this PR), there will be no error and everything will work correctly.

[glitch-txs]

have you tried using binding then?

[dima74]

have you tried using binding then?

Sorry what binding do you mean?

[glitch-txs]

how do you know it's a ref issue?

the Anchor class requires a Wallet Standard wallet, walletProvider is a completely custom class built by AppKit internally

[dima74]

how do you know it's a ref issue?

There will be no error and everything will work correctly without ref/reactive wrapping (e.g. using shallowRef as proposed in this PR)