Error: call revert exception When calling a read function

[adriandelgg]

Whenever I call a read function it causes a

Unhandled Runtime Error

Error: call revert exception (method="balanceOf(address)", errorArgs=null, errorName=null, errorSignature=null, reason=null, code=CALL_EXCEPTION, version=abi/5.3.1)

The contract shows that it indeed has the function available and that it's true it has a signer so I'm not sure why it keeps doing this error whenever I try to call a function to get its return value??

Also, whenever I do a transaction it will just allow me to send it without reverting from the require() statements I put.

Setting contract:

async function enableEth() {
    try {
	if (window.ethereum) {
		const provider = new ethers.providers.Web3Provider(window.ethereum);
		const [account] = await ethereum.request({
			method: 'eth_requestAccounts'
		});
		const signer = provider.getSigner(account);
		const contract = new ethers.Contract(
			'0x5FbDB2315678afecb367f032d93F642f64180aa3',
			artifact.abi,
			signer
		);
		setProvider(provider);
		setContract(contract);
		setAccount(account);
	} else if (window.web3) {
		console.log('Update MetaMask');
	} else {
		console.log('Enable MetaMask');
	}
   } catch (e) {
	  console.log(e);
   }
}

[zemse]

Your contract object shows methods (on JS side) based on the ABI you passed. If you're using a different network on metamask other than the one you should, and that other network does not have a contract deployed at that address, then eth_call fails (read call fail) while a transaction is processed costing just with intrinsic gas. This seems what you describe that only read calls fail. So can you confirm if you're on the right network?

[adriandelgg]

It seems the issue was that I was deploying to --network hardhat instead of localhost.

Anyone have any idea why it threw an error for that? I thought hardhat was a local network.

[zemse]

Oh, AFAIK in hardhat, localhost is simply any client that exposes JSON RPC http://localhost:8545 (can be hardhat node or ganache or geth --dev). While --network hardhat spins up a vm in memory and once your process exits, its gone. I think that explains why the contracts were not present at the address when your frontend tried to reach out :)

[naftalimurgor]

I ran into a similar issue, and I saw that I had connected to a different network (The Mainnet) while the smart contract I'm interacting with lives on the Rinkeby testnet