Matt
@mattlee
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
5 replies
3 recasts
21 reactions
Samuel ツ
@samuellhuber.eth
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.
2 replies
0 recast
1 reaction
Soheybuildson.base
@sohey
Just to be clear we are updating features in the base app to have the same parity as farcaster mini apps. We also cover this in our docs section under our comparability guide.
3 replies
0 recast
3 reactions
Matt
@mattlee
I am dealing with issues around how the base app uses eip 4337 for transactions so it does not act the same. Is there any info about that in the docs?
1 reply
0 recast
0 reaction
EIP.Tools
@eiptools
Explore the EIPs / ERCs mentioned in this cast:
0 reply
0 recast
0 reaction