Content
@
https://warpcast.com/~/channel/frames-v2
0 reply
0 recast
0 reaction
vrypan |--o--|
@vrypan.eth
What is the use of targetURL in a frame notification payload, if it can only be the frame URL? Even if you set it to something else, it will open the associated frame. It would be nice to at least be able to deep link to the frame (same domain, longer path). Or, ideally, be free to open an external URL. @horsefacts.eth, and insights?
1 reply
1 recast
4 reactions
horsefacts 🚂
@horsefacts.eth
It can be any URL on the frame domain. Or at least that’s the intent. If it’s not doing that now, might be a bug.
3 replies
0 recast
1 reaction
MOΞ
@moe
It’s working for us. We can link to any internal path in the frame notification.
1 reply
0 recast
3 reactions
vrypan |--o--|
@vrypan.eth
@horsefacts.eth, bug report: A notification with an empty targetUrl will crash Warpcast (both mobile and desktop) when clicked.
0 reply
0 recast
1 reaction
vrypan |--o--|
@vrypan.eth
Indeed, it's working on the frame domain. I would like it to be any URL. (It would allow my notification server, that is not hosted on the same URL as the frame, to track clicks.)
1 reply
0 recast
0 reaction
