Lesson 7: Rinkeby programmatic verification: NomicLabsHardhatPluginError: The constructor for contracts/FundMe.sol:FundMe has 1 parameters but 0 arguments were provided instead.

[knoori]

I'm having a problem with programmatically verifying the FundMe contract on the Rinkeby testnet. This issue is similar to discussion #207.

When I run yarn hardhat deploy --network rinkeby I get the following output:

❯ yarn hardhat deploy --network rinkeby
yarn run v1.22.15
[...]
deploy --network rinkeby
Nothing to compile
deploying "FundMe" (tx: 0x6837a9cb280d84d1fa676f593862382cca0112c8ac026274bfb6624247058485)...: deployed at 0x9D2396713C86BAe46d47e28A4b607cc98243CBc8 with 1038869 gas
Verifying contract...
contractAddress is 0x9D2396713C86BAe46d47e28A4b607cc98243CBc8
args is 0x8A753747A1Fa494EC906cE90E9f37563A8AF630e
Nothing to compile
Contract verification failed:
NomicLabsHardhatPluginError: The constructor for contracts/FundMe.sol:FundMe has 1 parameters
but 0 arguments were provided instead.
    at encodeArguments [...
]
Contract(s) deployed.
==================================================
✨  Done in 92.81s.

Note:

• this is for the refactored FundMe contract
• I've removed some extraneous terminal output, indicated by [...]
• the contract is successfully deployed
• the contract does not get successfully verified (i.e., the error is not an "already verified" error)
• the output suggests that hardhat verify is not receiving args, even though I've passed it
• I've logged contractAddress and args from verify.js, and both seem correct
• Increasing network.config.blockConfirmations (e.g. from 6 to 12) doesn't fix the issue

However, if I verify manually on the command line using yarn hardhat verify --network rinkeby 0x9D2396713C86BAe46d47e28A4b607cc98243CBc8 "0x8A753747A1Fa494EC906cE90E9f37563A8AF630e" I get:

❯ yarn hardhat verify --network rinkeby 0x9D2396713C86BAe46d47e28A4b607cc98243CBc8 "0x8A753747A1Fa494EC906cE90E9f37563A8AF630e"
yarn run v1.22.15
[...]
Nothing to compile
Successfully submitted source code for contract
contracts/FundMe.sol:FundMe at 0x9D2396713C86BAe46d47e28A4b607cc98243CBc8
for verification on the block explorer. Waiting for verification result...

Successfully verified contract FundMe on Etherscan.
https://rinkeby.etherscan.io/address/0x9D2396713C86BAe46d47e28A4b607cc98243CBc8#code
✨  Done in 27.20s.

Now the contract is successfully verified. So there seems to be an issue (at least on Rinkeby) when verifying using the verify.js script:

const { run } = require("hardhat")

async function verify(contractAddress, args) {
    console.log("Verifying contract...")
    console.log(`contractAddress is ${contractAddress}`) //db
    console.log(`args is ${args}`) //db
    try {
        await run("verify:verify", {
            address: contractAddress,
            constructor: args,
            // constructor: ["0x8A753747A1Fa494EC906cE90E9f37563A8AF630e"], //db
        })
    } catch (e) {
        if (e.message.toLowerCase().includes("already verified")) {
            console.log("Contract already verified.")
        } else {
            console.log("Contract verification failed:")
            console.log(e)
        }
    }
}

module.exports = { verify }

Any thoughts about what's going wrong? Thanks.

[knoori]

Solved this by fixing the typo in verify.js:
constructor -> constructorArguments

[Karakter99]

constructor -> constructorArguments: [args]
In my code did it like in the down.
constructorArguments: [args] == > constructorArguments: args

I deleted bracets from that code and it worked