Content
@
0 reply
0 recast
0 reaction
0xfeatr
@featr
Since this morning I've been getting this response when trying to navigate to a frame. This is happening through the warpcast dev tool. Some more context: I'm using frog's nextjs template through a proxy and that happens when calling https://client.warpcast.com/v2/fake-cast-frame-action Anyone got any ideas? 🙏
3 replies
0 recast
0 reaction
0xfeatr
@featr
There have been no changes on my code repo, so that leads me to believe it has something to do with a change on the endpoint? Is anyone else experiencing this
0 reply
0 recast
0 reaction
