Content
@
0 reply
0 recast
0 reaction
Tobias
@caruso33
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 recast
0 reaction
horsefacts
@horsefacts.eth
Frames are permanently cached at the time they are posted. So if you want to make changes without breaking existing frames, be careful about changing the layout or moving your message handler routes.
1 reply
0 recast
0 reaction
Tobias
@caruso33
Okay, I've reverted the changes. Wouldn't it be beneficial to have the flexibility to initiate caching at a later point? I feel the caching creates pain points for devs.
0 reply
0 recast
0 reaction
