It is very clear that the only way mini apps are going to work is to have one standardized testing environment. If a mini app works in this testing environment and not your farcaster client, then that is a bug in your client not the mini app. It will be increasingly unfeasible for mini app devs to debug every farcaster client separately

Team is looking to solve any interoperability paper cuts

Goal with mini apps is write once, deploy everywhere. No extra work required!

if you are building a mini app and are experiencing any compatiiblity issues between base and farcaster please respond with:

1. if you are using miniapp-sdk or minikit (base sdk)
2. what the problem is

please share as these come up, we are very focused on ensuring this is a good experience

It has dawned on me that as the creator of /tortoise I should probably upload all my music there.

I’m starting with a song called Lazy River. I released this in 2022 originally as part of a four song EP called Serene Wrap.

This is before I picked up guitar as my main writing tool, so it’s more piano/synthesizer based than other stuff you might have hear from me

There is a strange issue with collections on the original upload here because it was uploaded with base app. Investigating. I have reuploaded from farcastapp if you would like to collect tortoise.studio/song/lazy-river-2

I know yall are working on it and appreciate it! I am really struggling with getting song uploads to work on base app. I can't find any discrepencies between the create song transactions or data uploads between base app and farcaster app, but uploads from base app can't be collected. I've been combing through the logs in base app using eruda all morning(nightmare) and can't find a single discrepency in the transactions. Here is the upload from base app https://farcaster.xyz/mattlee/0xe37340c8

And here's the tx logs from that given to me by @pirosb3 

here's an upload from farcastapp which works fine

I work at the posts office

terminally.online

Forgot the tx logs

{
  "validation": {
    "status": "Error",
    "result_type": "Error",
    "description": "",
    "reason": "",
    "features": [],
    "error": "Simulation Error: Reverted",
    "labels": []
  },
  "simulation": {
    "status": "Error",
    "error": "Reverted"
  },
  "gas_estimation": {
    "status": "Error",
    "error": "Simulation Error: Reverted"
  },
  "block": "32999222",
  "chain": "base",
  "account_address": "0x1CeE629CeB06538874f30ead124c004CECBEb089"
}

I know yall are working on it and appreciate it! I am really struggling with getting song uploads to work on base app. I can't find any discrepencies between the create song transactions or data uploads between base app and farcaster app, but uploads from base app can't be collected. I've been combing through the logs in base app using eruda all morning(nightmare) and can't find a single discrepency in the transactions. Here is the upload from base app https://farcaster.xyz/mattlee/0xe37340c8

And here's the tx logs from that given to me by @pirosb3 

here's an upload from farcastapp which works fine https://farcaster.xyz/mattlee/0x6419873e

please share as these come up, we are very focused on ensuring this is a good experience

https://farcaster.xyz/dwr.eth/0xd9be11e7
https://farcaster.xyz/deodad/0x90352452

Dev ecosystem @farcaster, cofounder @bountycaster. Prev: cofounder of Scalar Capital, product at Coinbase, coproducer @ethereumfilm

#1 Simpsons Fan. 
/base-holland
/thesimpsons

🔵Base dev rel

Farcaster Development Boutique @ https://dTech.vision 💜 in love with tech 🤓decentralization, fitness and oldschool rap 😎

Nah. Means you can check what you can do in clients at least instead of guessing

Also there’s a compatibilities feature in the sdk today you can use to block / announce what you need to clients

But in the end you will never know it works across devices, screen sized and environments besides running it there

Typical frontend development issue.

Wouldn’t that still put the responsibility on mini app devs to debug multiple clients? Seems backwards to me. The responsibility should be on clients to be able to host mini apps that meet standards

yep, maybe I should setup a walletbeat / l2beat style compatiblity matrix that's hosted on a website and updated weekly as new features roll out across ?

cc @sohey @linda I'd be down to maintain this list, though would appreciate if we could agree to ping me on breaking changes :D

I don't have a git repo for the farcaster app client or TBA to automate any of the checks

I am though notified on all new frame sdk features so at least I can add these for sure.

🧙‍♂️🟨🟨🟨🟨🟨🐇💨🟨🐢🟨

That’s my hope but yikes trying to get any real answer from staff without being a cabal person has been a bummer.

They working on it it hasn’t even been a week. It’s not like that

I’m already fed up with trying to figure out what to do between Coinbase’s kit and Farcaster’s kit. I get it’s probably competition for DAU and money but like, we want to build. I’m sick of waiting for them to get over a marketing narrative sprint to get real productive answers meant for the small guys they keep saying they want to open doors for.

Composability is crypto’s dirty secret. 

(Other than a few top protocols there is none.)