metamask-mobile icon indicating copy to clipboard operation
metamask-mobile copied to clipboard

[Bug]: Raydium does not show a toast for MetaMask prior to connecting

Open vandan opened this issue 6 months ago • 4 comments

Describe the bug

The first time visiting Raydium.io/swap on Phantom and Solflare, the site provides a toast indicating that the wallet is in a disconnected state. It's unclear if MetaMask is explicitly taking an approach to avoid fingerprinting. Otherwise, it's not clear why MetaMask is not handled the same way (toast informing the user that the wallet is in a disconnected state).

Expected behavior

Toast message on Raydium.io/swap should be similar to Phantom & Solflare

Screenshots/Recordings

Image Image

Steps to reproduce

  1. Go to the in-app browser
  2. Open raydium.io/swap

Error messages or log output


Detection stage

On a feature branch

Version

7.46.99 (1901)

Build type

Other (please specify exactly where you obtained this build in "Additional Context" section)

Device

iPhone 16e

Operating system

iOS

Additional context

No response

Severity

No response

vandan avatar Jun 04 '25 05:06 vandan

It looks like other sites like jup.ag also show a toast message when the dapp is not connected to the wallet, yet.

vandan avatar Jun 04 '25 05:06 vandan

I'm not able to reproduce this issue. I tested with version 12.18.3 on desktop and 7.49.0 on mobile.

The wallet connected and wallet disconnected toasts were correctly displayed on my end

baptiste-marchand avatar Jun 17 '25 08:06 baptiste-marchand

Tested on 7.49.0 on mobile, and I am able to confirm what @baptiste-marchand shared.

https://github.com/user-attachments/assets/4cba6ecb-ae1a-4853-b185-f37174f07235

Doesn't seem to be an issue on the current release.

ffmcgee725 avatar Jun 17 '25 11:06 ffmcgee725

To clarify, the issue is present in the latest 7.49.0 (1977) build when visiting raydium.io/swap and jup.ag the first time. (compare to the experience on Phantom or Solflare)

vandan avatar Jun 17 '25 22:06 vandan

Closing this issue because it's not clear that the behavior difference is particularly problematic. Specifically for the disconnected state, we may not even want to automatically trigger such a notice.

vandan avatar Jun 23 '25 16:06 vandan