calling a function using ethers shows not a function in react

[sanchitdawarsd]

edited by @ricmoo; I've moved the relevant information from your linked issue.txt here

The buy method in the ABI throws an exceptions that it is not a method on the contract, with the following ABI:

const ABI = [
    // ...
    {
      "inputs": [
        {
          "internalType": "uint256",
          "name": "shareId",
          "type": "uint256"
        },
        {
          "internalType": "bytes",
          "name": "data",
          "type": "bytes"
        }
      ],
      "name": "buy",
      "outputs": [],
      "stateMutability": "payable",
      "type": "function"
    },
    {
      "inputs": [
        {
          "internalType": "uint256",
          "name": "shareId",
          "type": "uint256"
        }
      ],
      "name": "buy",
      "outputs": [],
      "stateMutability": "payable",
      "type": "function"
    }
]

const provider = await new ethers.providers.Web3Provider(window.ethereum);
const signer = await provider.getSigner();
const nftreseller = await new Contract(
    "0x8d0Fe38C4E0ba76c4070fB59D5659e5Bbb1072A3",
    ABI,
    signer
);
const tx = nftresellerr.buy(shareid, overrides);

[ricmoo]

Can you provide more details please? Code? ABI? Contract address? Network? :)

[sanchitdawarsd]

issue.txt

[ricmoo]

I've moved the relevant code from this linked file to the original discussion description.

[sanchitdawarsd]

pls refer this i have mentioned details in it

[ricmoo]

I am assuming you mean the method buy?

You have multiple definitions of buy in your ABI, so you need to specify which you mean. I highly recommend you trim down your ABI to just include the methods you use, but if you wish to keep the full ABI, you will need to use:

// There are two "buy" methers, so you must specify which you mean:
// - buy(uint256)
// - buy(uint256,bytes)
contract["buy(uint256)"](shareId, overrides)

If you trim down the ABI to exclude the ones you don't use, you will be able to have cleaner code (the code you have already would work) and you would cut about 2 megabytes off your application size, as most of that (massive) ABI is unused. :)

Just a suggestion though. :)

[vikramIde]

Every byte cost money on Ethereum good suggestion ;)

[zed-wong]

Thank you!

[amanmehra262001]

This worked thnq very much!!

[nickjuntilla]

This error should result in a message that there are 2 functions with the same name and fail completely or use one of them. This is an extremely unusual way to handle this situation where all the other functions work except the the ones that 'cancel each other out'. This makes it very difficult to debug because it looks like you're getting the wrong ABI file, something is cached, or not wired to the correct abi.

[zemse]

@nickjuntilla yes, ethers v6 it does that. here's an example of error for the scenario.

TypeError: ambiguous function description (i.e. matches "hello(uint8)", "hello(uint16)") (argument=
"key", value="hello", code=INVALID_ARGUMENT, version=6.6.2)

[suwandre]

I know this is a year old but I'm surprised how no one saw the mistype under

const tx = **nftresellerr**.buy(shareid, overrides);

change nftresellerr to nftreseller and your code should be good to go.