Content
@
0 reply
0 recast
0 reaction
Chris
@cmlad.eth
Frame v2 updates: - new context.client: fid of the client, whether frame is added, notification token+url - context.location: new type 'launcher' - manifest: new `imageUrl` and `buttonTitle` for rendering the frame outside of casts, please add soonish docs updated: https://docs.farcaster.xyz/developers/frames/v2/spec
6 replies
3 recasts
47 reactions
Chris
@cmlad.eth
`imageUrl` and `buttonTitle` will be required soon as they are critical for clients to be able to render your frame launcher on non-cast surfaces. Client SDK is updated: https://www.npmjs.com/package/@farcaster/frame-sdk Latest mobile app update generates the new manifest fields in Developer Tools > Domains
1 reply
1 recast
6 reactions
Ryan J. Shaw
@rjs
Hey Chris, can you explain this a bit more? What's the relationship between FrameConfig.imageUrl and FrameEmbed.imageUrl ? If I have an HTTP page with fc:frame -> FrameEmbed.imageUrl specificied, and a farcaster.json -> FrameConfig.imageUrl specified, I'm assuing FrameEmbed.imageUrl gets used right? I'm struggling to understand in which scenarios FrameConfig.imageUrl is useful?
0 reply
0 recast
0 reaction
