Problem in Publishing SimpleStorage Contract to Rinkeby Etherscan

[ZahraaHawie]

Hello!
(8:05:00) I have reached the part where I have to Verify & Publish Contract Source Code but I'm getting this error:

"We tried looking for a match from the list of compiled contract bytecode outputs (as listed below), but was unable to find an exact match"

my compiler was 0.8.13+ and I put pragma solidity ^0.8.8 .. in the Verify and Publish I choose compiler 0.8.8+ and it gives this error above.

so I reinstalled yarn add solc@0.8.7-fixed as you did.. changed my compiler workspace compiler version to 0.8.7 in VScode and I rename pragma solidity to 0.8.7.
I deployed it again (node deploy.js) and I tried different compilers 0.8.7 and 0.8.8 in the rinkeby etherscan and none of them work.. I think my problem is in the compiler but until now everything is fine with the tutorial.

// SPDX-License-Identifier: MIT

pragma solidity 0.8.7;

// pragma solidity ^0.8.0;
// pragma solidity >=0.8.0 <0.9.0;

contract SimpleStorage {
    uint256 favoriteNumber;

    struct People {
        uint256 favoriteNumber;
        string name;
    }
    // uint256[] public anArray;
    People[] public people;

    mapping(string => uint256) public nameToFavoriteNumber;

    function store(uint256 _favoriteNumber) public {
        favoriteNumber = _favoriteNumber;
    }

    function retrieve() public view returns (uint256) {
        return favoriteNumber;
    }

    function addPerson(string memory _name, uint256 _favoriteNumber) public {
        people.push(People(_favoriteNumber, _name));
        nameToFavoriteNumber[_name] = _favoriteNumber;
    }
}

Package.json:

{
  "dependencies": {
    "dotenv": "^16.0.1",
    "ethers": "^5.6.8",
    "fs-extra": "^10.1.0",
    "prettier": "^2.6.2",
    "prettier-plugin-solidity": "^1.0.0-beta.19",
    "solc": "0.8.7-fixed"
  },
  "scripts": {
    "compile": "yarn solcjs --bin --abi --include-path node_modules/ --base-path . -o . SimpleStorage.sol"
  }
}

Hope you can help!
Thank you

[PatrickAlphaC]

To be honest... just skip verifying manually on etherscan. It's a pain in the butt and we show you a much easier way to do it programmatically soon :)

[ZahraaHawie]

Yeah, thanks! but anyway I fixed it :)

[DorianDaSilva]

Ran into the same issue...Couldn't find a fix to it...Etherscan can be tricky to verify manually

[ZahraaHawie]

Hello Dorian, I fixed it yesterday and it works.. you just have to compile the contract again and run node deploy.js or as Patrick said no need to verify it manually. Goodluck