Content
@
https://warpcast.com/~/channel/frames-v2
0 reply
0 recast
0 reaction
hellno the optimist
@hellno.eth
can anyone help debug a frame that doesn't switch from splash color to the iframe content? video below ⬇️ Github repo https://github.com/frameception-v2/hellno.eth-keyflick .well-known/farcaster.json: https://hellnoeth-keyflick.vercel.app/.well-known/farcaster.json
3 replies
0 recast
0 reaction
Hoot 🎩
@owl
You’re probably missing the sdk.actions.ready() call?
2 replies
0 recast
1 reaction
hellno the optimist
@hellno.eth
you're probably right 😅😅😅😅
1 reply
0 recast
1 reaction
Hoot 🎩
@owl
tbh I hate that pattern. I get that it makes for better loading UX but it’s so anti web standards and complicates turning websites into frames💩 At least make it optional
1 reply
0 recast
1 reaction
hellno the optimist
@hellno.eth
yeah I was always calling it in other frames. the vibecoding got rid of it and I missed it 😂 seems a bit weird. the iframe wrapper can also recognize when the content is loaded without calling ready on the sdk.
1 reply
0 recast
0 reaction
Hoot 🎩
@owl
The idea is that you only call it when your async content is loaded so the user sees no loading state at all. But for the dev it’s just annoying and you will probably fall back to call it on load or on layout mount 😛
0 reply
0 recast
1 reaction
