Failed to check for transaction receipt

[BenAzlay]

When executing a transaction, I am listening for the 'receipt' event, like:

tx.on("receipt", (receipt) => {
    // Success logic
});

With Rabby, this throws the following error:

Transaction error: Error: Failed to check for transaction receipt:
{}
    at Object._fireError (index.js:74:1)
    at index.js:243:1

When testing with Metamask, I am not encountering this issue. Also, when using a custom RPC url on Rabby, I am not encountering this issue.

This makes me think the problem lies with the default RPC url of Rabby. This is not an issue of exceeding the RPC capacity as I originally supposed, because even first-time users of the dApp have the issue.

[Athensmo]

It proceed successfully here... are you certain you are not experiencing glitch on your end?

[BenAzlay]

The workaround I found was polling the receipt using my own RPC, like:

const receipt = await ownRpcWeb3.eth.getTransactionReceipt(txnHash);

For context, I am on Base and using Wagmi. I initialize the provider I use to sign transactions like:

const { connector: usedConnector } = useAccount();

const txnProvider = !!usedConnector.getProvider ? await usedConnector.getProvider() : window.ethereum;
setWeb3Provider(txnProvider);

I suspect this might be the origin of my issue, but that doesn't explain why, when using a custom RPC url on Rabby, I don't have the issue.

I also forgot to mention that for month, using the same code, I never encountered this issue using Rabby. It only started a few days ago. Has Rabby changed their default RPC provider? Which one are they using?

[vvvvvv1vvvvvv]

what is your tx.on("receipt" actually do?