Content
@
https://warpcast.com/~/channel/frames-devs
0 reply
0 recast
0 reaction
Zenigame
@zeni.eth
Solved the v2 frames metadata issue. Keeping the <providers> component in the layout.tsx file like in the tutorial seems to interfere with the fc:frame metadata generation. Solutions are either moving <providers> down the component stack (i.e., move it to a specific page) or creating a client layout that handles <providers>.
4 replies
1 recast
9 reactions
Zenigame
@zeni.eth
cc: @linda @horsefacts.eth I was having trouble getting the fc:frame metadata to generate correctly after following https://docs.farcaster.xyz/developers/frames/v2/getting-started My solution is above. Does it check out?
1 reply
0 recast
1 reaction
Zenigame
@zeni.eth
cc: @sarvesh371.eth - this was the problem I was running into
0 reply
0 recast
1 reaction
Samuel ツ
@samuellhuber.eth
which provider?
0 reply
0 recast
1 reaction
Sarvesh
@sarvesh371.eth
@samuellhuber.eth I am facing this issue https://warpcast.com/sarvesh371.eth/0x36c8e5c7 Thanks in advance if you can help!
0 reply
0 recast
1 reaction