Tony D’Addeo pfp
Tony D’Addeo
@deodad
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
15 replies
8 recasts
38 reactions

vrypan |--o--| pfp
vrypan |--o--|
@vrypan.eth
I have not pinpointed the source of the problem, but it seems like `sdk.wallet.getEthereumProvider()` does not work as expected for me.
3 replies
0 recast
2 reactions

dylan pfp
dylan
@dylsteck.eth
@vrypan.eth following back up here, was debugging with @wool and we’re pretty sure this is because the function(which the sdk sets internally) uses getCapabilities which isn’t in the beta yet. that will land internally today/tomorrow and by some time early next week when another beta goes out getChains, getCapabilities, and getEthereumProvider will all work out of the box for you!
1 reply
0 recast
1 reaction

Tony D’Addeo pfp
Tony D’Addeo
@deodad
what library are you using what behavior are your experiencing when making this call are you experiencing this problem in base farcaster or both?
1 reply
0 recast
0 reaction

dylan pfp
dylan
@dylsteck.eth
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
1 reply
0 recast
1 reaction