frames-devs

is anyone else having trouble deploying frames with frog? im not sure if i should disable devtools or what but I can't render my frames using WC validator but it shows up fine using devtools.

Do the images have complex layouts? Frog encodes the image state in the image URL. If it gets too large the URL can exceed the max HTTP header size and start to fail. You can use a separate image handler to avoid this.

(cc @dalechyn.eth  who can correct me where I'm wrong, some of this might have changed)

23. Co-founder of @beliefs - @launchtokenbot (beliefs.social). Collaborator at /frogfm.

Do the images have complex layouts? Frog encodes the image state in the image URL. If it gets too large the URL can exceed the max HTTP header size and start to fail. You can use a separate image handler to avoid this.

(cc @dalechyn.eth  who can correct me where I'm wrong, some of this might have changed)

https://frog.fm/concepts/image-handler

I'm eth newbie..just learning
(working on @farcaster)

terminally.online

Yea I got img handlers for the complex images. I'll see if the http headers check out still

Yes. This was done because in the past, the function was called twice since there's two requests sent each time.
1 for the actual frame
1 for the image
This means a frame that updates or toggles state will do so twice. Encode the image was the way to avoid this since it just decodes and return rather than run the entire frame handler