Error on Verify and Publish Contract Source Code.

[Arinze-Odukwe]

Patrick Collins, thank you for creating this massive course. So, as a follow-up to lesson 5, I tried to verify and publish the contract source code on Rinkeby Etherscan, but it keeps displaying in the compiler output tab...

Compiler debug log:
 Error! Unable to generate Contract ByteCode and ABI
 Found the following ContractName(s) in source code : SimpleStorage
 But we were unable to locate a matching bytecode (err_code_2)
 For troubleshooting, you can try compiling your source code with the [Remix - Solidity IDE](https://remix.ethereum.org/) and check for exceptions

What could be wrong😕?

[Equious]

You're unable to import scripts when manually verifying. I think you need to remove the import and paste the whole contract into your submission (flatten your code).

[PatrickAlphaC]

I'd need more information on what you're doing.

1. Send screenshot of every screen on etherscan
2. What does your code look like

Or... you could just skip verifying. Verification gets a lot easier when we get to hardhat.

[vaasanthk]

I got the same error. The screenshot below shows the error and I copied the same solidity code from github and pasted it into the contract source code.

[PatrickAlphaC]

Yeah, I'd just skip manual verification for now. The manual verification is sort of a pain in the butt.

[vaasanthk]

Sure, Thanks Patrick!

[mattjaf]

Mine instantly verified without having to enter any information on etherscan, when I deployed it from remix. It maybe possible that its throwing an error because a contract with that exact byte code has already been verified on etherscan.

When you view the contract code on etherscan, does it say verified and show you the goods?

[vaasanthk]

Ya when you deploy the contract from remix you don't have to entire any information it's already verified. When I deploy from vs code I run into this problem, I think as you said it may have already been verified for that byte code.

[Equious]

I ask, because it generally doesn't ERROR if it recognizes the byte code. It just says "similar blah blah exists" or whatever.

…

On Sun., Jun. 12, 2022, 4:22 a.m. vaasanthk, ***@***.***> wrote: Ya when you deploy the contract from remix you don't have to entire any information it's already verified. When I deploy from vs code I run into this problem, I think as you said it may have already been verified for that byte code. — Reply to this email directly, view it on GitHub <#120 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASHIK5GS6D7H5C2B4I2KH6LVOW27TANCNFSM5X2DOEZQ> . You are receiving this because you commented.Message ID: <smartcontractkit/full-blockchain-solidity-course-js/repo-discussions/120/comments/2932129 @github.com>

[Equious]

Have you flattened your code? If you're verifying manually on etherscan, it won't recognize imports. You have to add those full contracts to your source.

…

On Sun., Jun. 12, 2022, 4:22 a.m. vaasanthk, ***@***.***> wrote: Ya when you deploy the contract from remix you don't have to entire any information it's already verified. When I deploy from vs code I run into this problem, I think as you said it may have already been verified for that byte code. — Reply to this email directly, view it on GitHub <#120 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASHIK5GS6D7H5C2B4I2KH6LVOW27TANCNFSM5X2DOEZQ> . You are receiving this because you commented.Message ID: <smartcontractkit/full-blockchain-solidity-course-js/repo-discussions/120/comments/2932129 @github.com>