if you are building a mini app and are experiencing any compatiiblity issues between base and farcaster please respond with:

1. if you are using miniapp-sdk or minikit (base sdk)
2. what the problem is

@farcaster dev / dad / books, cooks, ski, code ~ there are many things of which a wise man might wish to be ignorant

I have not pinpointed the source of the problem, but it seems like `sdk.wallet.getEthereumProvider()` does not work as expected for me.

Dad, geek, conversation liquidity provider. vrypan.net | @l--o--l | $lemon3 | https://farcaster.xyz/miniapps/Ufj2_Hsf5Hlb/what-did-i-miss

this is on our(Base App’s) end, we don’t support that function yet but we still pass an 1193 injected provider you can even use with just window.ethereum I’m pretty sure 

separately we’ll add support for getEthereumProvider directly I just don’t have an ETA for you yet

ok if you can write up something here I will add it the docs so users have a workaround

would be great to get this fixed asap

not at my laptop rn so can’t fully confirm(will in the next hour or so) but I don’t think we are passing the sdk.wallet object back yet, just pronouncing the 1193 injected provider(I haven’t used window.ethereum in a while but think it might be able to use this?)

could provide a code snippet that is a reasonable workaround for now that works for getting a provider in either client?

does sdk.wallet.ethereum work?