Content
@
https://warpcast.com/~/channel/frames-v2
0 reply
0 recast
0 reaction
Johns | johnsgresham.eth
@johns
Right now Rainbowkit ConnectButton shows QR codes for connecting wallets in a Frame in Warpcast on mobile. This is because Rainbowkit detects isMobile boolean by finding "iPhone" in the browser's navigator.userAgent. Warpcast sets it as just "warpcast". I think warpcast should set userAgent to something like "warpcast; iPhone" or "warpcast; android" or just prefix "warpcast" to the existing mobile userAgent. cc @horsefacts.eth does this seem right?
3 replies
1 recast
1 reaction
Johns | johnsgresham.eth
@johns
example
0 reply
0 recast
0 reaction
Johns | johnsgresham.eth
@johns
And Rainbowkit isMobile() code https://github.com/rainbow-me/rainbowkit/blob/0c9679812123e17b45e1330d5e3b665b48c82864/packages/rainbowkit/src/utils/isMobile.ts#L25
0 reply
0 recast
0 reaction
Daniel Sinclair
@danielsinclair
I think you'll see this flow because `window.ethereum` isn't detectable; usually we handle that to support mobile dApp browsers. A little behind on this, but I think we should be able to add support by adopting the Frame connector, similarly to our default support for auto-connecting in the Safe browser. Should be able to release it later this week. https://www.npmjs.com/package/@farcaster/frame-wagmi-connector
1 reply
0 recast
1 reaction