Content
@
0 reply
0 recast
0 reaction
Jacob
@jrf
gm the @basedmoji frame is working on supercast, but not on warpcast ... does anyone have any idea why this is happening? p.s. @ornamental is launching another one soon... thanks :-) https://www.supercast.xyz/c/0x5319c7b03b96b11a565ab6bed3dcfc1744570499 https://warpcast.com/0xconca.eth/0x5319c7b0
3 replies
1 recast
3 reactions
Daniel - Bountycaster
@pirosb3
I had a similar experience with Bountycaster. It turned out that our frame had too many characters in the placeholder input field, Warpcast is pretty strict (as per spec) on the constraints of the frame. Open up your inspector and look at where the error is coming from
2 replies
0 recast
2 reactions
conca π©π€
@0xconca.eth
thank you for your reply! The thing is that we don't have any input field π so maybe I stumbled upon a similar "nasty" bug, but a different one nonetheless....? Was Warpcast's Frame Validator working just fine when you encountered this bug?
1 reply
0 recast
0 reaction
Daniel - Bountycaster
@pirosb3
We found the bug before using the frame validator. Did you check that everything in your OG tags meets the spec?
1 reply
0 recast
1 reaction
conca π©π€
@0xconca.eth
The validator reacts as expected, which is so annoying because you'd think you'd get the same result as the debugger! But no... π I am using Frog, so it kinda handles metas on its own... the frame worked for days with people using it and recasting it, then it suddenly stopped and I've been trying to understand why
0 reply
0 recast
1 reaction
