Lesson 8: unable to call fund

[NotNotRama]

This is what I currently have in index.js

import { ethers } from "./ethers-5.6.esm.min.js"
import { abi, contractAddress } from "./constants.js"

const connectButton = document.getElementById("connectButton")
const fundButton = document.getElementById("fundButton")
connectButton.onclick = connect
fundButton.onclick = fund

async function connect() {
    if (typeof window.ethereum !== "undefined") {
        await window.ethereum.request({ method: "eth_requestAccounts" })
        document.getElementById("connectButton").innerHTML = "Connected!"
        console.log("connected!")
    } else {
        document.getElementById("connectButton").innerHTML =
            "Please install metamask"
        console.log("No metamask!")
    }
}

async function fund() {
    const ethAmount = "77"
    console.log(`Funding with ${ethAmount}..`)

    if (typeof window.ethereum !== "undefined") {
        const provider = new ethers.providers.Web3Provider(window.ethereum)
        const signer = provider.getSigner()

        const contract = new ethers.Contract(contractAddress, abi, signer)
        const transactionResponse = await contract.fund({
            value: ethers.utils.parseEther(ethAmount),
        })

        console.log("transactionResponse", transactionResponse)
    }
}

For contractAddress, I'm using the address where the contract was deployed at

deploying "FundMe" (tx: 0x647a9bb72a9ff39dd9e44804e95921ec89a358493d993426eac047cf97e9966a)...: deployed at 0xe7f1725E7734CE288F8367e1Bb143E90bb3F0512 with 1064162 gas

and the abi is the one found in the previous project.

I can click the fund button and the metamask modal pops up, but when I accept the transaction, I get the following error when console logging transactionResponse

And on the terminal, I get this

[mattjaf]

oh, this looks like its cuz your using hardhat node and you put some miles on the test account they gave you.

you can use a different account or try setting the nonce for the transaction before sending it.

You can pass it as the second params in an object to the contract method

[NotNotRama]

I tried using a different account, and while the console log error disappeared, I still get this on the terminal where I executed yarn hardhat node

Also, how do I exactly pass the nonce in the contract? Something like this?

await contract.fund({
      value: ethers.utils.parseEther(ethAmount),
      nonce: 2,
 })

[NotNotRama]

So apparently, by the time I click the fund button I get this error

But the metamask modal pops up, accept the transaction and get the following response showed in the console log (no error this time)

Maybe I should also add that when running the tests, they all pass.

[JamesMckenna]

@NotNotRama

Did you get this figured out? I suspect that the multiple calls, eth_call Contract call: FundMe#<unrecognized-selector> is an issue with metamask triggering the RPC call multiple times (before I click the Confirm button, and also after I click the Confirm button) and has nothing to do with your smart contract. When I yarn hardhat run scripts/fund.js and yarn hardhat run scripts/withdraw.js I don't get any errors or extra RPC calls. It is only when I use the UI and Metamask.

metamask is somehow triggering multiple calls to the fund function. Since 1 of the calls goes through, additional calls will have a null value for await contract.fund({ value: ethers.utils.parseEther(ethAmount)}); and cause the Error: VM Exception while processing transaction: reverted with reason string 'Didn't send enough!'

You can check out these posts:
#315
https://stackoverflow.com/questions/72101643/hardhat-what-are-the-strange-calls-to-my-smart-contract
https://ethereum.stackexchange.com/questions/135108/wagmi-usecontractwrite-eth-call-transaction-reverted-function-selector-wa

[NotNotRama]

Sorry for the late response! (was busy with some IRL stuff)

Going back to your question: no, I have yet to find a solution for this. Apparently, the app doesn't break because of that error, although I'd prefer to find a solution for it.

Also, it seems that this error was already discussed here #315