Skip to content

useWaitForTransactionReceipt returning null for transaction using paymasterService #4626

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 task done
encryptedDegen opened this issue Apr 11, 2025 · 0 comments
Open
1 task done

Comments

@encryptedDegen
Copy link

Check existing issues

Describe the bug

I have a checkout flow that supports sponsoring the gas using the paymasterService.
When I initiate a transaction using writeContractsAsync I extract the hash afterwards and add it to my transaction object, which is then used to feed the transaction hash to the useWaitForTransactionReceipt hook.

After that's done, the transaction is stuck pending, never returns an error. Network tab confirms it by endless null results from the RPC calls.

I have made sure that the hash is valid (looking it up on basescan was successful), and that the chain given to the hook matches the one transaction was done on.

Example of the RPC calls:

Image
Image

Expected behaviour

Executing transactions using walletClient.writeContract works perfectly fine, and would expect to work the same when using writeContractAsync

Link to Minimal Reproducible Example

https://stackblitz.com/edit/new-wagmi-fkukg35a

Steps To Reproduce

Connect to an account abstracted wallet (I use coinbase smart wallet).

Make sure you have added a valid paymaster link and have verified the 0x41Aa48Ef3c0446b46a5b1cc6337FF3d3716E2A33 contract for it.

Initiate the transaction and check the console where the states from useWaitForTransactionReceipt will be displayed, and check the network tab to see the coresponding RPC calls-

What Wagmi package(s) are you using?

wagmi

Wagmi Package(s) Version(s)

2.14.16

Viem Version

2.26.3

TypeScript Version

5.3.3

Anything else?

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant