Major error with DApp, resulting in the application freezing during minting.

[tdev00]

Hi all.

I'm having issues minting using the DApp. It seems as though minting over 10 NFTs at 100 MATIC or 100000000000000000000 WEI per NFT, throws an error. What seems to solve the issue is when the price is less than 100 MATIC.
The specific error code is as follows:
"Error: [number-to-bn] while converting number "1.3e+21" to BN.js instance, error: invalid number value. Value must be an integer, hex string, BN or BigNumber instance. Note, decimals are not supported. Given value: "1.3e+21""

I believe the source of the issue is the claimNFTs() function. Does anyone have an idea of how to fix this?

[NoWeiBruh]

having same error right now

[hamzahoda]

having same error.

[mike7user]

Hi all.

I'm having issues minting using the DApp. It seems as though minting over 10 NFTs at 100 MATIC or 100000000000000000000 WEI per NFT, throws an error. What seems to solve the issue is when the price is less than 100 MATIC. The specific error code is as follows: "Error: [number-to-bn] while converting number "1.3e+21" to BN.js instance, error: invalid number value. Value must be an integer, hex string, BN or BigNumber instance. Note, decimals are not supported. Given value: "1.3e+21""

I believe the source of the issue is the claimNFTs() function. Does anyone have an idea of how to fix this?

This can be a few issues.
ONE:
HERE is a link on converting your price from big numbers to small numbers. Use a [Eth to Wei converter] (https://eth-converter.com/) to get the correctly proportioned eth price.

or

TWO:
You may have the incorrectly addressed the ".mint" function. Try reviewing back to see what call name you labeled the function during contract deployment and ensure that the to are one and the same. A common issue would be ".saleMint" value in SmartContract.sol and a ".mint" value in the App.js. obviously, They need to be the same for the imported contract to communicate with the Dapp script.

THREE:
You may be inputting the big number value incorrectly. This link may help you understand how to format the value to get the correct output.

Goodluck. If I notice your reply, I will respond asap. The struggle is real! Keep on truckin!