frames-devs

Is something wrong with debugger.framesjs.org? I have been trying to test my frame, but after the 1st frame the subsequent ones are failing with a 500, internal server error

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

Web2, Web3 hustler | Building the collaboration protocol @ottp

@v I'm having a tough time debugging my frames. The debugger.framesjs loads the first frame, but upon a click on a button the post errors with 500 internal error (unexpected end of json input).

And warpcaster embedding tool takes me to the download screen as opposed  to the test app. Could you or somebody help please?

yes there is something wrong with the hosted debugger rn. very close to a fix, would recommend running locally

Building FOSS via @frames, /open-frames to help decentralized social win. a16z CSX23. farcasterchannels.com farcaster.id

Thank you David and Varun. Is there a way I can test the frames on the warpcast client without actually casting it?

hosted debugger has just been fixed & also there's a new local one

I have been using the local one and it works great, except for user inputs to persist across frames.

Could it be the browser? 

Also, I thought there was a frame debugger specifically for the warpcast client, isn't it?