frames-devs
A place for frames devs to ask questions and help eachother. This is not a place for shilling or launching frames.
Sophia pfp
0 reply
1 recast
9 reactions
Linda Xie pfp
1 reply
0 recast
28 reactions
Kevin pfp
1 reply
2 recasts
11 reactions
Papajams pfp
0 reply
0 recast
6 reactions
dusan pfp
3 replies
0 recast
5 reactions
Tayyab - d/acc pfp
0 reply
0 recast
6 reactions
Darryl Yeo 🛠️ pfp
1 reply
1 recast
7 reactions
dusan pfp
1 reply
0 recast
1 reaction
Carl Gustaf 👨🏼‍💻 pfp
1 reply
0 recast
0 reaction
Peter Kim pfp
3 replies
2 recasts
12 reactions
carlos pfp
2 replies
0 recast
2 reactions
Barbs pfp
4 replies
12 recasts
21 reactions
pfp
Reporting a potential V1 frame bug that could result to losing funds. Problem: @awedjob submitted a transaction via our v1 frame, which should have been submitted on @base; however the user was prompted to sign a transaction on the mainnet, which resulted in funds getting locked up in the contract. Context: https://warpcast.com/awedjob/0x7429d31d Potential Issue: I believe `switchNetwork` is not being properly called after initial wallet connection. To Reproduce: I was able to reproduce it, which shows in the screen recording below. You can see three different attempts in chronological order: 1. The wallet was already connected - tx works as expected ✅ 2. The wallet was already connected & was on a different network - switches network and tx works as expected ✅ 3. I disconnect the wallet, and connect the wallet when requested - tx attempts to be processed on mainnet, which is not expected ❌ cc: @v @dwr.eth @horsefacts.eth @woj.eth @deodad @linda
25 replies
2 recasts
14 reactions
Temitope pfp
0 reply
0 recast
3 reactions
doug pfp
0 reply
0 recast
2 reactions