Bug: Transaction Execution Error, Fundless Transaction to Burn Address

[natesena]

Describe the bug

Wallet does not execute transaction

Steps

1. Use the coinbase wallet ios app.
2. Browse to eternal.social
3. Connect the wallet. Go to eternal.social/feed
4. Hit the "post" button.
5. Type text in the modal. Hit submit button
6. See error:
   TransactionExecutionError: An internal error was received. Request Arguments: from: 0x774069eCF05892e7667FD18B1Edb4645c273351e to: 0x0000000000000000000000000000000000000000 value: 0 ETH data: 0x54657374696e6720636f696e626173652077616c6c657420696f732062726f77736572 gas: 21726 Details: Failed to sign transaction Version: 2.21.1.

Expected behavior

I would expect the transaction to flow through. It seems the app thinks I have "failed to sign transaction" when I have definitely signed the transaction before the transaction execution.

Version

No response

Additional info

Desktop

No response

Smartphone

iphone 15 pro max

[cb-jake]

Hi @natesena thanks for flagging. I have tried to repo but was unable to. Can you provide more info about how the transaction is constructed. What chain you were using, and any other pertinent info? Thanks.

[natesena]

Hi Jake, The issue lies within the coinbase wallet app on iPhone. On my app, eternal.social the transaction never goes through. Here is a video of the process not working: https://drive.google.com/file/d/1uGIJjuamIw2in8GhEOejRfLldqDvd0Io/view?usp=sharing More or less it fails silently. Appreciate you looking into this - Coinbase Wallet would be my ideal flow for users to have the best experience before launch. Nate

…

On Tue, Oct 29, 2024 at 12:10 PM cb-jake ***@***.***> wrote: Hi @natesena <https://github.com/natesena> thanks for flagging. I have tried to repo but was unable to. Can you provide more info about how the transaction is constructed. What chain you were using, and any other pertinent info? Thanks. — Reply to this email directly, view it on GitHub <#1435 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABTATFTNGU6OAKDHCYC3NP3Z56XOPAVCNFSM6AAAAABQNRSYXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBUG4ZTCNBQGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[cb-jake]

Interesting. What version of the app are you using. When I first tested I used the mobile to desktop connection (ie walletlink). I just tested with the in app browser and that worked as well. I used mainnet and base on the two tests

[natesena]

The version I have currently is 29.16.0

…

On Tue, Oct 29, 2024 at 3:24 PM cb-jake ***@***.***> wrote: Interesting. What version of the app are you using. When I first tested I used the mobile to desktop connection (ie walletlink). I just tested with the in app browser and that worked as well. I used mainnet and base on the two tests — Reply to this email directly, view it on GitHub <#1435 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABTATFUCJYNB7WGAPOWCK7DZ57OFBAVCNFSM6AAAAABQNRSYXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBVGE2DANBRG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[cb-jake]

I'm using the same version. Is there a specific network you're using? Also, have you tried using the QR code to connect via walletlink? Curious if we can narrow down the issue to the connection type.

[cb-jake]

Going to close due to inactivity. Please re-open if you have a sufficient way to reproduce. Thanks