Error: call revert exception CALL_EXCEPTION

[ghost]

Describe the bug
I am getting an revert exception in my React app even the created instance exists. At const exchange = await this.getExchange(exchangeAddress); the error occurs. For a while it had worked and then it didn't anymore. I could not reproduce the error. Testing with Hardhat against local network.

  import Exchange from '../abi/src/contracts/Exchange.sol/Exchange.json';
                ....
                ....
               .....
  getExchange = async (exchangeAddress: string) => {
    const exchange = new ethers.Contract(
      exchangeAddress,
      Exchange.abi,
      this.state.signer
    );
    return exchange;
  };

Is consumed in:

  getTokenAmount = async (ethAmount: string) => {
    try {
      const exchangeAddress =
        await this.state.factory.callStatic.createExchange(
          REACT_APP_TOKEN_ADDRESS,
          {
            from: this.state.account,
          }
        );

      const exchange = await this.getExchange(exchangeAddress); 
      console.log(exchange) // <-- the exchange instance exists in the browser console
      const res = await exchange.getTokenAmount(ethAmount);// <- throws revert exception

      return res;
    } catch (err) {
      console.log(err);
    }
  };

Reproduction steps
ABI for Exchange contract:
https://github.com/melonecrypto/meloneswap/tree/main/src/abi/src/contracts/Exchange.sol

Error in Browser

Error: call revert exception (method="getTokenAmount(uint256)", errorArgs=null, errorName=null, errorSignature=null, reason=null, code=CALL_EXCEPTION, version=abi/5.4.0)
    at Logger.makeError (index.ts:213)
    at Logger.throwError (index.ts:225)
    at Interface.decodeFunctionResult (interface.ts:425)
    at Contract.<anonymous> (index.ts:332)
    at Generator.next (<anonymous>)
    at fulfilled (index.ts:2)

Environment:
OS: MAC OS Big Sur
Editor: VS-Code
Testing-Environment: Hardhat : 2.5.0 localhost: url: 'http://127.0.0.1:8545'
Package.json

[zemse]

Are you sure that your contract is deployed in the same network that your this.state.signer is connected to? To confirm you can try doing this.state.signer.provider.getCode(exchangeAddress) to see if it returns some bytecode for your contract.

[FavyTeam]

Awesome! Good answer! Kudos!

[mon842]

i am also getting the same error. My signer address and contract address both are different what should I do now?
And what do you mean by 'same network'?

[etabebe1]

I observed the same error but the reason occurred in my case were, I deployed the contract two or more times which resulted in change of Address of the Contract since I used the first contract address as constant I couldn't interact with my contract using the previous Address. To fix I only re-deployed the contract once again these time I used the Contract Address i got from the deployment

[oscarsernarosero]

I am having the same issue. My project has been working for several months just fine. I decided to upload my project to be hosted on fleek on July 27th. I am using hardhat, and the only modification I had to do was to install ethers in the frontend library (I am not sure if this is the source of my error. I might've just configure the context in Fleek). Anyways, I stopped working on it for several days (busy on other stuff), and now that I am trying to launch the app in my localhost blockchain, it doesn't work.

index.ts:213 Uncaught (in promise) Error: call revert exception (method="getOwner()", errorArgs=null, errorName=null, errorSignature=null, reason=null, code=CALL_EXCEPTION, version=abi/5.4.0)
    at Logger.makeError (index.ts:213)
    at Logger.throwError (index.ts:225)
    at Interface.decodeFunctionResult (interface.ts:425)
    at Contract.<anonymous> (index.ts:332)
    at Generator.next (<anonymous>)
    at fulfilled (index.ts:2)

[georgemac510]

This worked for me. TY

[venkat1705]

TY

[krunal4Tanthetaa]

this is working

[oscarsernarosero]

Nevermind. I was deploying my dapp in the local host, but my wallet was set to mainnet. Just switched to localhost and that fixed it.

[joshfisidi]

lol wow, I appreciate you keeping us updated

[pr0ph0z]

I also didn't realize this 🤦‍♂️. Thanks for pointing out!

[ricmoo]

(moving to discussions)

[villarode]

I deployed on polygon ok a few days ago and everything was right I'm trying to do exactly the same changing only the max number of NFTs available in the contract and it fails to even compile:

$ npx hardhat run scripts/run.js --network polygon

Compiling 15 files with 0.8.4
Solidity compilation finished successfully
Contract deployed to: 0xD8F0C83513AaA3aAde3B7BF016ca999CEDe4961E
9 NFTs have been reserved
Error: call revert exception (method="tokensOfOwner(address)", errorArgs=null, errorName=null, errorSignature=null, reason=null, code=CALL_EXCEPTION, version=abi/5.5.0)
at Logger.makeError (C:\Users\User\nft-collectible\node_modules@ethersproject\logger\src.ts\index.ts:225:28)
at Logger.throwError (C:\Users\User\nft-collectible\node_modules@ethersproject\logger\src.ts\index.ts:237:20)
at Interface.decodeFunctionResult (C:\Users\User\nft-collectible\node_modules@ethersproject\abi\src.ts\interface.ts:425:23)
at Contract. (C:\Users\User\nft-collectible\node_modules@ethersproject\contracts\src.ts\index.ts:392:44)
at step (C:\Users\User\nft-collectible\node_modules@ethersproject\contracts\lib\index.js:48:23)
at Object.next (C:\Users\User\nft-collectible\node_modules@ethersproject\contracts\lib\index.js:29:53)
at fulfilled (C:\Users\User\nft-collectible\node_modules@ethersproject\contracts\lib\index.js:20:58)
at processTicksAndRejections (node:internal/process/task_queues:96:5) {
reason: null,
code: 'CALL_EXCEPTION',
method: 'tokensOfOwner(address)',
errorArgs: null,
errorName: null,
errorSignature: null,
address: '0xD8F0C83513AaA3aAde3B7BF016ca999CEDe4961E',
args: [ '0xD561Fd6763e8cc8c7603C0D7971Bc003DD2Dd17d' ],
transaction: {
data: '0x8462151c000000000000000000000000d561fd6763e8cc8c7603c0d7971bc003dd2dd17d',
to: '0xD8F0C83513AaA3aAde3B7BF016ca999CEDe4961E',
from: '0xD561Fd6763e8cc8c7603C0D7971Bc003DD2Dd17d'
}
}

And furher on, if I try to verify:

$ npx hardhat verify --network polygon 0xD8F0C83513AaA3aAde3B7BF016ca999CEDe4961E "ipfs://QmWKW6nqqHnpRoUVjnNeLE46KaDfy2oMWAysCt7qjmk8nz/"

Error in plugin @nomiclabs/hardhat-etherscan: The address 0xD8F0C83513AaA3aAde3B7BF016ca999CEDe4961E has no bytecode. Is the contract deployed to this network? The selected network is polygon.

what can it possibly be? Cheers

[ricmoo]

You should contact Hardhat. Ethers does not provide any compilation services, so if it is failing to compile, it is something further up the stack.

[villarode]

Thanks mate. What's truly strange is that the code is unchanged from a few days ago when all was well.... Did they have any changes at Hardhat over the past 4 days or so?

[ricmoo]

I don’t know. I am not affiliated with that project in any way.

[villarode]

also, strange thing is that compilation itself apparently gets done successfully:

$ npx hardhat run scripts/run.js --network polygon
Compiling 15 files with 0.8.4
Solidity compilation finished successfully
Contract deployed to: 0xD8F0C83513AaA3aAde3B7BF016ca999CEDe4961E
9 NFTs have been reserved

And then Hell breaks loose((((

[villarode]

Could it be a gas issue? Gas was extremely high on Plolygon at the ime

[villarode]

Could it be that the process is still in the making with the contracts, just queued?

Nonce Position 30 21 - does this have anything to do with the issue?

or may be it is that I used up all the gas I somehow allocated for the deploying and it just stopped at such gas prices?

Gas Limit: 21,052
Gas Used by Transaction: 21,052 (100%)

I am asking because on Rinkeby (I returned back to testnet) everything is just fine.....

on Mumbai Polygon testnet it also deploys and verifies just fine, with flying colours......

[isiakaabd]

Its probably because you are using different test network. for example, if you used e.g rinkeby to deploy your contract and switched to mainnet when using it, that error will occur

[mastrobardo]

the error occurs regardless

[luncht1me]

We're having an issue right now where our WRITE transactions are going thru the embedded metamask provider and thus to the proper localhost devnet RPC we have configured...

But when we READ with same initialization, getting this exception.
Are READ methods not using the same provider?? Seems kind of weird that there'd be a different default provider for reading that needs to be manually configured to point to the appropriate network... But to Write everything seems fine.

[zemse]

The read calls should be sent to metamask provider as well if write calls are being sent, unless somehow another provider is coming in between. Do you have a logic that fallbacks to another provider if metamask is not present? If that's the case, it's possible that the provider is sneaking in unknowingly. Lmk if the problem still exists.

[LKW679]

Unhandled Rejection (Error): call revert exception [ See: https://links.ethers.org/v5-errors-CALL_EXCEPTION ] (method="TokenID()", data="0x", errorArgs=null, errorName=null, errorSignature=null, reason=null, code=CALL_EXCEPTION, version=abi/5.6.4)

is there any solution for this problem?

[yasindunethmina]

I think finally I found the solution for this error!

Error: call revert exception [ See: https://links.ethers.org/v5-errors-CALL_EXCEPTION ], data="0x", errorArgs=null, errorName=null, errorSignature=null, reason=null, code=CALL_EXCEPTION, version=abi/5.7.0)

*You must not start either your react or next project or anything else before following this, so before doing anything just restart VSCode and clear your terminal!

First go to your project directory and run npx hardhat node
Then run npx hardhat run --network localhost scripts/deploy.js (Without this step, whole thing won't work!)
Then run npm start if you're working with react or npm run dev if you're on next js.
Check your app on localhost:3000 in a new browser window.

It's important to start your project following each steps in order, otherwise I always got the above error.

[Adi-21]

bro I had done the same thing but still I got this issue after implementing this command npm run dev

Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:71:19)
at Object.createHash (node:crypto:133:10)
at BulkUpdateDecorator.hashFactory (C:\Users\adis2\OneDrive\Desktop\NFT\polygon-ethereum-nextjs-marketplace\node_modules\next\dist\compiled\webpack\bundle5.js:133863:18)
at BulkUpdateDecorator.update (C:\Users\adis2\OneDrive\Desktop\NFT\polyzation error' ], library: 'digital envelope routines',
reason: 'unsupported', code: 'ERR_OSSL_EVP_UNSUPPORTED'}

[Pranjul120568]

it didn't work bro

[Pranjul120568]

How did u solved this?

[Vinimart]

Thanks bro, it worked for me!

[Jayakumar2812]

This also happens when you make an external view call but the function modifies the state.

[Galact07]

Describe the bug I am getting an revert exception in my React app even the created instance exists. At const exchange = await this.getExchange(exchangeAddress); the error occurs. For a while it had worked and then it didn't anymore. I could not reproduce the error. Testing with Hardhat against local network.

  import Exchange from '../abi/src/contracts/Exchange.sol/Exchange.json';
                ....
                ....
               .....
  getExchange = async (exchangeAddress: string) => {
    const exchange = new ethers.Contract(
      exchangeAddress,
      Exchange.abi,
      this.state.signer
    );
    return exchange;
  };

Is consumed in:

  getTokenAmount = async (ethAmount: string) => {
    try {
      const exchangeAddress =
        await this.state.factory.callStatic.createExchange(
          REACT_APP_TOKEN_ADDRESS,
          {
            from: this.state.account,
          }
        );

      const exchange = await this.getExchange(exchangeAddress); 
      console.log(exchange) // <-- the exchange instance exists in the browser console
      const res = await exchange.getTokenAmount(ethAmount);// <- throws revert exception

      return res;
    } catch (err) {
      console.log(err);
    }
  };

Reproduction steps ABI for Exchange contract: https://github.com/melonecrypto/meloneswap/tree/main/src/abi/src/contracts/Exchange.sol

Error in Browser

Error: call revert exception (method="getTokenAmount(uint256)", errorArgs=null, errorName=null, errorSignature=null, reason=null, code=CALL_EXCEPTION, version=abi/5.4.0)
    at Logger.makeError (index.ts:213)
    at Logger.throwError (index.ts:225)
    at Interface.decodeFunctionResult (interface.ts:425)
    at Contract.<anonymous> (index.ts:332)
    at Generator.next (<anonymous>)
    at fulfilled (index.ts:2)

Environment: OS: MAC OS Big Sur Editor: VS-Code Testing-Environment: Hardhat : 2.5.0 localhost: url: 'http://127.0.0.1:8545' Package.json

Use this instead of Web3Provider,
const provider = new ethers.providers.JsonRpcProvider();

[mertcankose]

Everything is okay, deployed contract network fit the wallet network. And it works that i want to write contract but external view calls gives me this error. Why? Write okey View throw an error..

[Linhy1009]

I'm also experiencing the same problem, the strange thing is that there is no problem with my contract address, and I am connected to the correct metamask account, but my alchemy update information very slow, and my error is as follows:

Error: call revert exception [ See: https://links.ethers.org/v5-errors-CALL_EXCEPTION ] (method="getVpk(address)", data="0x", errorArgs=null, errorName=null, errorSignature=null, reason=null, code=CALL_EXCEPTION, version=abi/5.7.0)
    at Logger.makeError (/home/linhy/dMAABE/node_modules/@ethersproject/logger/src.ts/index.ts:269:28)
    at Logger.throwError (/home/linhy/dMAABE/node_modules/@ethersproject/logger/src.ts/index.ts:281:20)
    at Interface.decodeFunctionResult (/home/linhy/dMAABE/node_modules/@ethersproject/abi/src.ts/interface.ts:427:23)
    at Contract.<anonymous> (/home/linhy/dMAABE/node_modules/@ethersproject/contracts/src.ts/index.ts:400:44)
    at step (/home/linhy/dMAABE/node_modules/@ethersproject/contracts/lib/index.js:48:23)
    at Object.next (/home/linhy/dMAABE/node_modules/@ethersproject/contracts/lib/index.js:29:53)
    at fulfilled (/home/linhy/dMAABE/node_modules/@ethersproject/contracts/lib/index.js:20:58)
    at processTicksAndRejections (node:internal/process/task_queues:95:5) {
  reason: null,
  code: 'CALL_EXCEPTION',
  method: 'getVpk(address)',
  data: '0x',
  errorArgs: null,
  errorName: null,
  errorSignature: null,
  address: '0xd75ff285006f706E752Fe1e1d71CbBaD23E8F301',
  args: [ '0x304c7F6eB466591EBc41291b91A1A60bD559be85' ],

Here is my code：

addr = await ethers.getSigners();
  for(let i=0; i< bn; i++){
    AttributeAuthContract[i] = await new ethers.Contract("0xd75ff285006f706E752Fe1e1d71CbBaD23E8F301",abi,addr[i]);
    addrstr[i] = addr[i].address;
    console.log("Account balance:", (await addr[i].getBalance()).toString());
  }

  let start = Date.now();
  console.log(`time to start to calculate a user's attribute = ${start} `);
  let ins;
  userAuthAttr[0] = "";
  for(let i=0; i < bn; i++){
    ins = await AttributeAuthContract[i].getVpk(addrstr[i]);
    console.log(ins);
    
    pklist[i] = ins[0];
    ins = await AttributeAuthContract[0].getAuthorization(addrstr[i], addrstr[0]);
    let rcode = ins[0];
    if(0 == rcode){
      let tempSig = ins[1];
      let tempDigest = ins[2];
      let tempAttr = ins[3];
      if(secp256k1.ecdsaVerify(unserialize(tempSig), unserialize(tempDigest), unserialize(pklist[i]))){
        userAuthAttr[0] += tempAttr.replace(/;/g," ") + " ";
      }
    }
  }
  let end = Date.now();
  let time = end - start;
  console.log(`response time for calculating a user's attribute = ${time} MS`);

  console.log(userAuthAttr[0]);
  }

I have a couple of other js files but they all work fine, I really don't know what the reason is, I hope someone knows what the problem is.
qwq

[akhil888binoy]

I'm also experiencing the same problem, the strange thing is that there is no problem with my contract address, and I am connected to the correct metamask account, but my alchemy update information very slow, and my error is as follows:

Error: call revert exception [ See: https://links.ethers.org/v5-errors-CALL_EXCEPTION ] (method="getVpk(address)", data="0x", errorArgs=null, errorName=null, errorSignature=null, reason=null, code=CALL_EXCEPTION, version=abi/5.7.0)
    at Logger.makeError (/home/linhy/dMAABE/node_modules/@ethersproject/logger/src.ts/index.ts:269:28)
    at Logger.throwError (/home/linhy/dMAABE/node_modules/@ethersproject/logger/src.ts/index.ts:281:20)
    at Interface.decodeFunctionResult (/home/linhy/dMAABE/node_modules/@ethersproject/abi/src.ts/interface.ts:427:23)
    at Contract.<anonymous> (/home/linhy/dMAABE/node_modules/@ethersproject/contracts/src.ts/index.ts:400:44)
    at step (/home/linhy/dMAABE/node_modules/@ethersproject/contracts/lib/index.js:48:23)
    at Object.next (/home/linhy/dMAABE/node_modules/@ethersproject/contracts/lib/index.js:29:53)
    at fulfilled (/home/linhy/dMAABE/node_modules/@ethersproject/contracts/lib/index.js:20:58)
    at processTicksAndRejections (node:internal/process/task_queues:95:5) {
  reason: null,
  code: 'CALL_EXCEPTION',
  method: 'getVpk(address)',
  data: '0x',
  errorArgs: null,
  errorName: null,
  errorSignature: null,
  address: '0xd75ff285006f706E752Fe1e1d71CbBaD23E8F301',
  args: [ '0x304c7F6eB466591EBc41291b91A1A60bD559be85' ],

Here is my code：

addr = await ethers.getSigners();
  for(let i=0; i< bn; i++){
    AttributeAuthContract[i] = await new ethers.Contract("0xd75ff285006f706E752Fe1e1d71CbBaD23E8F301",abi,addr[i]);
    addrstr[i] = addr[i].address;
    console.log("Account balance:", (await addr[i].getBalance()).toString());
  }

  let start = Date.now();
  console.log(`time to start to calculate a user's attribute = ${start} `);
  let ins;
  userAuthAttr[0] = "";
  for(let i=0; i < bn; i++){
    ins = await AttributeAuthContract[i].getVpk(addrstr[i]);
    console.log(ins);
    
    pklist[i] = ins[0];
    ins = await AttributeAuthContract[0].getAuthorization(addrstr[i], addrstr[0]);
    let rcode = ins[0];
    if(0 == rcode){
      let tempSig = ins[1];
      let tempDigest = ins[2];
      let tempAttr = ins[3];
      if(secp256k1.ecdsaVerify(unserialize(tempSig), unserialize(tempDigest), unserialize(pklist[i]))){
        userAuthAttr[0] += tempAttr.replace(/;/g," ") + " ";
      }
    }
  }
  let end = Date.now();
  let time = end - start;
  console.log(`response time for calculating a user's attribute = ${time} MS`);

  console.log(userAuthAttr[0]);
  }

I have a couple of other js files but they all work fine, I really don't know what the reason is, I hope someone knows what the problem is. qwq

did anybody solve this issue?

[aniketghavte]

having the same issue but mine was because at the hardhat deployment i have used localhost
then i tried to Sepolia and it works