getting Uncaught (in promise) Error: invalid BigNumber when calling SC method from reactBug Report Title

[ashish077]

Ethers Version

"ethers": "^5.6.9"

Search Terms

ethers.utils.parseEther

Describe the Problem

I am getting the following error when hitting metamask from react app for a smart contract method. The peculiar thing about this error is it is working fine in few system and in few it is failing with the below error. I am also mentioning the method for which it is giving the error.

Code Snippet

const requestService = async (selectedId, id, capacity, limit, account) => {
  // console.log("selectedId",selectedId,"id",id,"capacity",capacity,"account",account);
  // console.log(window.ethereum);
  console.log("limit:", limit);
  console.log("capacity", capacity);
  const res = await P2P.methods
    .requestService(
      parseInt(selectedId),
      parseInt(id),
      parseInt(capacity),
      ethers.utils.parseEther(String(limit))
    
    )
    .send({
      from: account,
      gas: 2000000,
    });
  console.log("response", res);
  return res;
};

Contract ABI

No response

Errors

index.ts:261 Uncaught (in promise) Error: invalid BigNumber string (argument="value", value="NaN", code=INVALID_ARGUMENT, version=bignumber/5.6.2)
    at e.value (index.ts:261:28)
    at e.value (index.ts:273:20)
    at e.value (index.ts:277:21)
    at Function.value (bignumber.ts:238:27)
    at Function.value (bignumber.ts:250:30)
    at a.value (number.ts:25:27)
    at array.ts:71:19
    at Array.forEach (<anonymous>)
    at x (array.ts:54:12)
    at a.value (tuple.ts:54:16)

Environment

Ethereum (mainnet/ropsten/rinkeby/goerli)

Environment (Other)

No response

[ricmoo]

If you look at the error you will see that NaN is being passed in, which is certainly not a valid value. :)

[ashish077]

It is on ropsten

[ricmoo]

That doesn’t matter. It isn’t a network error. You are passing an invalid value into parseEther. You can’t pass NaN in. Parse ether expects a string.

[ashish077]

Hi richard,
thanks for your reply.
So it is not the NaN as it is giving that error even when I just pass a parseInt(som-integer-number). It is failing before it even reaches sc as it fails in the metamask wallet only. However I dont think it is an issue with ethers. Its either web3 the package which I am using to hit the sc method or metamask wallet itself.

[ricmoo]

The function parseEther MUST receive a string. It converts string values like "0.1" into a BigNumber. You cannot pass in a parseInt(blah), since that is a number, not a string.

If you call parseInt("foo") you get NaN, so you may be passing in a non-numeric string.

[ashish077]

not in parseEther just parseInt as a value as in instead of " ethers.utils.parseEther(String(limit))" i did "parseInt(4)" it still failed with that bigNumber error.