Anyone seeing an issue with a frame route not being valid if it doesn’t have a trailing slash? This is using frog with next.js. E.g caststorage.com doesn’t work but caststorage.com/ does!

Engineer @ Syndicate, prev: Rainbow, Foundation & Cloudflare /poetic-web, builds caststorage.com

building products /neynar, hacking /farhack, yapping /dylan | dylansteck.com

Yeah I am using getMetadata. Does it sound like it’s an issue with the library or the underlying frames or warpcast?

yeah have seen issues with that before, are you using the getMetadata function from frog?

personally have seen the function be slightly more reliable on framesjs but yeah it’s def annoying to colocate your frame in react/nextjs

In the end it just started working again. I think it was an issue on warpcasts end that they then fixed

Just came across this — I have the exact same issue just in reverse. Doesn't work with trailing slash, works without. Did you ever find a solution?