Content
@
0 reply
0 recast
0 reaction
Brandon 🛡️ 🎩
@bn
I just updated Warpcast on Android, and now a lot of frame images are not displaying correctly. Anyone else experiencing this? The same frames work fine in a browser.
3 replies
1 recast
4 reactions
Brandon 🛡️ 🎩
@bn
For example
1 reply
0 recast
1 reaction
elboletaire 🗳️
@elboletaire.eth
Can you confirm me if you can see rendered frames 2, 4, 8 and 11 in the following link? https://warpcast.com/elboletaire.eth/0xe4fb1d89 If you can see them, it seems like the issue is with base64 encoded images.
2 replies
0 recast
0 reaction
Brandon 🛡️ 🎩
@bn
I can see 2, 5, 8, and 11. Though my frames that aren't rendering don't use data URIs.
1 reply
0 recast
1 reaction
elboletaire 🗳️
@elboletaire.eth
Are you using proper png or jpg files? Other's I seen failing, like paragraph ones, were using invalid image file formats, like avif
1 reply
0 recast
0 reaction
Brandon 🛡️ 🎩
@bn
https://daily-gwei-links.vercel.app/frame
2 replies
0 recast
0 reaction
elboletaire 🗳️
@elboletaire.eth
I think you have the links to the images broken, and we're seeing a cached one in some devices (like in desktop). Here's the URL cached, which works: https://maglit.me/rechenib And here's the one you currently have defined in your frame:image: https://maglit.me/pobuate This one returns a bad request 🧐
1 reply
0 recast
1 reaction
Brandon 🛡️ 🎩
@bn
The only difference between those two links is the 2nd one encodes the first `&` in the query string for some reason. Where did you pull that value from? I don't think it is a caching issue because all the frames after the initial frame are dynamic.
1 reply
0 recast
0 reaction
