any idea what the error `Expected union value at path /icon` on the composer-action validator means? Composer actions seem to be fine with the frames.js debugger.
- 13 replies
- 0 recasts
- 1 reaction
Hi, there's some strange warpcast behaviour going on. With a new app version, I changed the page indexing of our multipage frames app. When using the warpcast frames debugger the page progression works fine. However, already casted frames now navigate weirdly presumably because of having still the former page indexing, which they shouldn't have according to the debugger? 🤔 Is each page in a multi-page frame somehow cached, even the page is not used as a shared linked? Do I need to timestamp every page? Or is there another underlying issue going on? https://warpcast.com/~/developers/frames?url=https%3A%2F%2Fsecretcaster.datalatte.com%2Fframes%3Fpage%3DCircleCastShared%26cast_id%3Db764e133-c134-4769-8922-06da52f48e06%26timestamp%3D1725633274222 vs. https://warpcast.com/amirmabhout/0x19095883
- 8 replies
- 1 recast
- 3 reactions
Hi, there's some strange warpcast behaviour going on. With a new app version, I changed the page indexing of our multipage frames app. When using the warpcast frames debugger the page progression works fine. However, already casted frames now navigate weirdly presumably because of having still the former page indexing, which they shouldn't have according to the debugger? 🤔 Is each page in a multi-page frame somehow cached, even the page is not used as a shared linked? Do I need to timestamp every page? Or is there another underlying issue going on? https://warpcast.com/~/developers/frames?url=https%3A%2F%2Fsecretcaster.datalatte.com%2Fframes%3Fpage%3DCircleCastShared%26cast_id%3Db764e133-c134-4769-8922-06da52f48e06%26timestamp%3D1725633274222 vs. https://warpcast.com/amirmabhout/0x19095883
- 1 reply
- 0 recasts
- 0 reactions