transaction error when the second NFT to be mint

[jianguda]

Thanks for sharing such a great NFT market implementation! However, I found a hidden but critical issue, that is when the second NFT to be mint, the MetaMask always claims a transaction error.

I tried to debug the contract but sadly I failed to find the real cause :< so I decide to report the issue to you!

Best!

[jianguda]

@devpavan04

[devpavan04]

@jianguda can you share the metamask error.

[Yorzaren]

@jianguda Depending on how you create the second token, you might run into an issue with the colours not being unique.

If you did something like me you'd end up getting a nondescript contract error with metamask because of the colour issue.

Token 1: You shift some of the colour selectors but leave a few as default. Token gets created. Token 2: You shift some of the colour selectors but leave a few as default. (At least one colour is not unique) Contract fails.

It comes from this part of the CryptoBoys.sol and isn't bug.

    // loop through the colors passed and check if each colors already exists or not
    for(uint i=0; i<_colors.length; i++) {
      require(!colorExists[_colors[i]]);
    }

There should be some sort of warning/popup about the colour not being unique but that message might have been missed by you. Try making sure that the colours you are using for each CryptoBoy is unique/set. Hopefully that resolves the issue you were seeing.

[trandinhthang14]

@jianguda I have an error connecting the wallet. Can you show me this step? "CRYPTO BOYS CONTRACT NOT DEPLOYED TO THIS NETWORK. Connect Metamask to Kovan Testnet Or Localhost 7545 running a custom RPC like Ganache."