Phantom Wallet is not working in Chrome but works in Firefox

Embedded Wallets (Web3Auth)
1 
Hi MetaMask team,

We are facing an issue where Phantom Wallet is not working in Chrome, while it works as expected in Firefox.

We have also confirmed that the same issue can be reproduced on the official MetaMask developer/demo site:
https://ew-demo.metamask.io/

Platform/Browser:
Web application using Chrome and Firefox.

Issue:
- Phantom Wallet does not work as expected in Chrome.
- The same Phantom Wallet flow works correctly in Firefox.
- We can reproduce the issue on the MetaMask developer/demo site as well.

Could you please confirm whether this is a known compatibility issue between Phantom Wallet and Chrome?

Also, please let us know if there is any recommended configuration, workaround, or fix required to make Phantom Wallet work correctly in Chrome.

We can provide Chrome console errors/logs and our SDK/package versions if required for further investigation.

Thanks!
2

Hi @osizdevtm2_demo thanks for sharing all the details. Did you talk to Phantom team too?

3

Hi Shana, thanks for following up.

We haven’t contacted the Phantom team yet. We wanted to first confirm whether this could be related to the MetaMask SDK integration or wallet connector initialization on our side.

4

Thanks for the follow-up — happy to help get this to the right place in the Builder Hub.

Two things going on here:

  1. Routing: Since you’re referring to MetaMask SDK / wallet connector initialization, this falls under the MetaMask Connect category rather than Embedded Wallets. Could you repost (or ask a mod to move the thread) here: MetaMask Connect - MetaMask Builder Hub — that team can take a direct look at your connector setup.

  2. Phantom specifically: Since Phantom is a third-party extension, any Chrome-vs-Firefox behavior differences are ultimately on their end. What we can help verify is whether your connector/provider-discovery logic (e.g., EIP-6963 multi-wallet discovery) is correctly picking up injected providers in Chrome — that’s worth raising in the MetaMask Connect thread. When you post there, please include your connector configuration, the SDK/connector version, and what window.ethereum (or the discovered provider list) looks like in Chrome vs. Firefox.

If this turns out to actually be an Embedded Wallets issue — for instance, something related to social/email login or the embedded signer rather than an injected extension — just reply here with those details and I’ll pick it up in this category.

Note: This response was generated by an AI bot and may require further verification. The MetaMask Community Team has tracked this issue and will be responding as soon as possible.

5

Hi shana, thanks for the clarification.

Yes, we have specifically observed that Phantom works correctly in Firefox but does not work in Chrome with our current integration.

Since the issue appears to be browser-specific, we’ll raise this under the MetaMask Connect category as suggested and include our connector configuration, SDK/connector version, and the provider discovery details from both Chrome and Firefox.

We’ll also check with the Phantom team to confirm whether there are any known Chrome-specific issues on their side.

Thanks for pointing us in the right direction.

6

Thanks for confirming, Shana — that all makes sense.

A Chrome-vs-Firefox difference in third-party wallet detection is best handled in the MetaMask Connect category, so please open a thread there: MetaMask Connect - MetaMask Builder Hub

Including your connector configuration, the SDK/connector version, and the provider discovery output (EIP-6963 announced providers) from both Chrome and Firefox is exactly the right information to attach — that will let us compare what each browser is announcing. Checking with the Phantom team in parallel is also a good call, since this could be Chrome-specific extension behavior on their end.

If it turns out this is actually an Embedded Wallets question after all, just reply here and we’ll pick it back up in this category.

Note: This response was generated by an AI bot and may require further verification. The MetaMask Community Team has tracked this issue and will be responding as soon as possible.

8

Sorry for the issue with the bot, because of the confusion of the product it thought you wanted to use metamask connect for phantom integration.

Can you share some logs when this issue happens? I am able to connect to my test phantom wallet that is why I am asking for the browser console logs and what is says for your case.

9

Hi,

The issue while connecting phantom wallet with chrome on solana network that time facing this issue

Error Message on browser console log

The app’s signature request cannot be shown due to invalid formatting.

10

I have raised this request with the development team, I will get back to you when this is fixed.

11

Fixed in the latest sdk

1 Like