useWaitForTransaction unusual behavior using hash & wait config

[YannikSood]

I am using useWaitForTransaction like so:

const { data: waitData, isLoading: waitLoading } = useWaitForTransaction({
      hash: writeData?.hash,
      wait: writeData?.wait,
      onSettled(data, error) {
        console.log("Settled", { data })
      }
    });

Using the hash config, onSettled logs fine.

However, if I comment out the hash config, and just use the wait config instead, I get the following error:

The problem is, I need to use the wait config. Using the wait config adds additional properties to the TransactionReciept. From the ethers docs:

If the wait() method on the returned TransactionResponse is called, there will be additional properties on the receipt:

receipt.events - an array of the logs, with additional properties (if the ABI included a description for the events)
receipt.events[n].args - the parsed arguments

My write function emits an event, and I need to get this event in the receipt. So, the wait configuration not working in useWaitForTransaction is very inconvenient.

I am using wagmi version ^0.4.1. I have used an older version that worked fine with the same logic, but after having to update wagmi due to using RainbowKit, the latest version has caused this problem. Can anyone help me solve this?

Thanks in advance.

[YannikSood]

This is the write function btw:

const { data: writeData, error: writeError, write } = useContractWrite(
      {
        addressOrName:  ContractAddress,
        contractInterface: ContractInterface,
      },
      'entry',
      { 
        args: [firstAnswer.trim().toLowerCase(), secondAnswer.trim().toLowerCase()],
          overrides: { 
            value: ethers.utils.parseEther("0.01") 
         }
      }
    )