<100 subscribers
When I launched my Mini App at https://nexart.xyz/miniapp, everything appeared correct. The domain was verified, Warpcast previewed the embed perfectly, and the metadata passed all validation checks. But even after casting the link, nothing showed up in Coinbase Wallet’s feed. No splash, no frame, no Mini App.
So I started digging. Here’s a breakdown of what I tried, what failed, and what finally made it work — not as a definitive Coinbase guide, but as a technical discovery others might find useful.
{
"version": "1",
"imageUrl": "https://nexart.xyz/api/embed-image",
"button": {
"title": "Open NexArt",
"action": {
"type": "launch_miniapp",
"url": "https://nexart.xyz/miniapp"
}
}
}This worked in Warpcast, but Coinbase Wallet seemed to ignore it. Switching to a fc:frame setup using split tags and a post action fixed it:
<meta name="fc:frame" content="vNext" />
<meta name="fc:frame:image" content="https://nexart.xyz/api/embed-image" />
<meta name="fc:frame:button:1" content="Open NexArt" />
<meta name="fc:frame:button:1:action" content="post" />
<meta name="fc:frame:button:1:target" content="https://nexart.xyz/miniapp" />That alone made a noticeable difference.
At first, I tried embedding everything in a single JSON string under fc:frame, like:
<meta name="fc:frame" content='{"version":"vNext",...}' />But Coinbase didn’t seem to parse that correctly. Switching to the individual split meta tags for fc:frame:image, button:1, action, and so on is what eventually validated.
This one caught me off guard. When I ran:
curl -H "User-Agent: FarcasterBot" https://nexart.xyz/miniappI got a 301 Moved Permanently to https://www.nexart.xyz/miniapp. That redirect was enough to break metadata detection in some clients.
Once I removed the redirect and ensured that the casted URL (https://nexart.xyz/miniapp) responded directly with metadata, the Coinbase feed started picking it up.
If you’re using https://yourwebsite.xyz/miniapp, double-check that bots don’t get redirected to a www. or https variant — they may not follow it.
Coinbase seems to require that the exact domain you cast is also the domain embedded in the metadata. If you cast yourwebsite.xyz/miniapp but all your meta points to www.yourwebsite.xyz, the frame may silently fail to appear.
After making these changes, the Mini App began appearing reliably in my Coinbase Wallet feed — complete with:
Splash screen
Button
Working deep link to /miniapp
Change | Result |
|---|---|
Used launch_frame post action | Frame became visible |
Switched to fc:frame split tags | Metadata validated |
Removed www. redirects | Feed parsed correctly |
Matched cast domain to metadata URLs | Indexing succeeded |
I don’t claim to know exactly how Coinbase Wallet indexes Farcaster Frames, but these tweaks worked for me. If your Mini App isn’t showing up, start by checking:
Whether you’re using split fc:frame tags
Whether you’re casting the exact URL that responds with metadata
Whether there are any HTTP redirects in place
Whether you’re using launch_frame instead of launch_miniapp
While these changes made the Mini App visible in my own Coinbase Wallet feed, I can’t say with certainty that they’re universally sufficient. The indexing behavior still feels somewhat opaque — and it’s possible that other factors (timing, domain age, caching, or internal heuristics) influence whether a frame is picked up and rendered.
I’m continuing to test and document how Coinbase Wallet handles Farcaster Mini App metadata, especially when it comes to refresh timing, cast re-parsing, and splash behavior. If you’ve encountered similar issues — or found a more reliable indexing pattern — I’d love to hear about it.
Feel free to use nexart.xyz/miniapp as a working reference if you’re troubleshooting your own setup.
Arrotu