appkit does not inject a provider into window.etherum if we choose google login

[javaspeak]

appkit does not inject a provider into window.etherum if we choose google login

If I chose metamask in appkit window.ethereum is populated. Why is it not populated when I choose the google login option.

Should I be do this?:

const { walletProvider } = useAppKitProvider('eip155');
(window as any).ethereum = walletProvider as unknown as Eip1193Provider;

I pray this question is answered - looks like reown devs are not look much at this discussion forum and I cannot seem to get through all the hoops necessary to join reown's discord channel.

Can this be escalated so we have the chance of getting some better support?

Thank you for your time.

[tomiir]

Hi @javaspeak !
window.ethereum is used by extension wallets to expose themselves to the dapps.
AppKit's embedded wallet lives in an iframe and injecting to the parent window has some serious security concerns.

As you mention, the appropiate way of accessing the provider is using

const { walletProvider } = useAppKitProvider('eip155');

Is there a specific reason you need window.ethereum ? Why not use the provider directly?
Let us know and we can help you navigate your use case!

[rohit-710]

Hey @javaspeak - I believe that my colleague @tomiir has already answered your question and has a few follow up questions.

I tested out all of the Discord invites embedded within our docs, website and the blog; all of them seem to work as expected. What issue are you facing when you click on the Discord invite?