Bug: Intermittent errors using TransactionButton with CB Browser Wallet

[dry-tortuga]

I'm seeing intermittent errors when using the TransactionButton to initiate a new contract call via Coinbase Browser Wallet at songbirdz.cc. See the 2 screenshots below for the specific errors in my console, but it takes me a few times clicking on the button before I can succesfully get Coinbase Browser Wallet to open up with the new contract call.

You can see the relevant code here: https://github.com/dry-tortuga/songbirdz-collection-frontend/blob/main/src/components/BirdIdentificationModal.js#L135

A contributing factor could be that I need to wait for the result of an async API call before I can fully build the contracts=[{ ... }] prop that is passed to Transaction, so wondering if that could be causing an issue?

Any better workarounds for this kind of use case?

What's the expected behavior?

Clicking on the TransactionButton should initiate the transaction request in the Coinbase Browser Wallet for final confirmation on the first click attempt.

What version of the libraries are you using?

• [email protected]

[dry-tortuga]

It looks like it's using the wallet_sendCalls method which isn't supported in non smart wallets?

[Zizzamia]

Thank you for sharing this information. We are currently adding new listeners to access more lifecycle data from the Transaction component, which should make debugging easier.

I will ping you as soon as it's ready.

[dry-tortuga]

Thank you for sharing this information. We are currently adding new listeners to access more lifecycle data from the Transaction component, which should make debugging easier.

I will ping you as soon as it's ready.

Thank you! Yes please let me know as people are running into this error which is blocking them from using the app :)

I ended up just adding a check for now to only use the TransactionButton if they have smart wallet!

[Zizzamia]

With the latest v0.29.1 you will have access to the onStatus hook, which helps listen all status happening inside the Transaction experience.

Now, it needs more polishing, so your case scenario actually is perfect for us, so we can learn more about those edge cases.

Would you mind use the onStatus hook, add a console.log and just report back all the logging you have when you use the Transaction experience.

Something I am looking to learn is, where in the flow things start breaking, and what's the diffence of experience between Smart Wallet and EOA for your app.

[mykcryptodev]

It looks like onchainkit's Transaction component is trying to use wallet_sendCalls regardless if the wallet has that capability or not. If that's the case, using the Transaction button for an EOA isn't possible.

Here is an example where I am attempting to allow an EOA to approve USDC to a contract and it is trying to use wallet_sendCalls for the EOA

[dry-tortuga]

With the latest v0.29.1 you will have access to the onStatus hook, which helps listen all status happening inside the Transaction experience.

Now, it needs more polishing, so your case scenario actually is perfect for us, so we can learn more about those edge cases.

Would you mind use the onStatus hook, add a console.log and just report back all the logging you have when you use the Transaction experience.

Something I am looking to learn is, where in the flow things start breaking, and what's the diffence of experience between Smart Wallet and EOA for your app.

Sounds good! I'll work on that this week and get back to you.

[Zizzamia]

And @dry-tortuga, just FYI, we did not drop this. We have @abcrane123 pairing with @mykcryptodev in the next few days to keep exploring how to best share the errors when someone uses EOA instead of Smart Wallet.