Retrieving with balanceOf on ERC20 contract has CALL_EXCEPTION meanwhile transferTo works with no error

[emclab]

I am having an embarrassing CALL_EXCEPTION with ERC20 contract balanceOf after re-deploying the contract. Here is the code in nodejs retrieving balance of an ERC20 contact with ethersjs 5.7 (just upgraded from 5.5) after re-deploying the contract:

const { ContractFactory } = require('@ethersproject/contracts');
    const { ethers } = require('ethers');
    router.get("/feeacctbalance", async(req, res) => {
        //let wallet = new ethers.Wallet(process.env.privateKeyThis); 
        let acctAddress = process.env.feeAddress;  //<<==wallet address
        let acctPrivKey = process.env.feeAcctPrivateKey;  
        if (!acctAddress || !acctPrivKey) return res.status(401).send("Missing fee acct address/private key");
        if (!global.contractFYX) return res.status(401).send("Missing FYX contract");
        let contractFYX = global.contractFYX;  //<<==ERC20 contract
        let provider = global.provider;  //<<== provider
        try {
            let a = await contractFYX.balanceOf(acctAddress);
            a = a/10**18; //bigNumber returned
            a = a.toFixed(2); //(parseInt(a.toString())/10**18).toFixed(2) return 0.00. .toFixed() shall be done with a number.
            console.log("Acct balance in number : ", a); 
            //
            return res.status(200).send({balance:a, fyxAddress:contractFYX.address, feeAddress:acctAddress});
        } catch(err) {
            console.log("Error in feeacctbalance to : ", err);  //<<==error throws here
            return res.status(400).send("error in fee acct balance check")
        }
    });

Here is error thrown.

Error in feeacctbalance to :  Error: call revert exception (method="balanceOf(address)", errorArgs=null, errorName=null, errorSignature=null, reason=null, code=CALL_EXCEPTION, version=abi/5.5.0)
        at Logger.makeError (/Users/macair/Documents/code/js/xjc_bbone/node_modules/@ethersproject/logger/lib/index.js:199:21)
        at Logger.throwError (/Users/macair/Documents/code/js/xjc_bbone/node_modules/@ethersproject/logger/lib/index.js:208:20)
        at Interface.decodeFunctionResult (/Users/macair/Documents/code/js/xjc_bbone/node_modules/@ethersproject/abi/lib/interface.js:384:23)
        at Contract.<anonymous> (/Users/macair/Documents/code/js/xjc_bbone/node_modules/@ethersproject/contracts/lib/index.js:390:56)
        at step (/Users/macair/Documents/code/js/xjc_bbone/node_modules/@ethersproject/contracts/lib/index.js:48:23)
        at Object.next (/Users/macair/Documents/code/js/xjc_bbone/node_modules/@ethersproject/contracts/lib/index.js:29:53)
        at fulfilled (/Users/macair/Documents/code/js/xjc_bbone/node_modules/@ethersproject/contracts/lib/index.js:20:58)
        at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
      reason: null,
      code: 'CALL_EXCEPTION',
      method: 'balanceOf(address)',
      errorArgs: null,
      errorName: null,
      errorSignature: null,
      address: '0x8C4B.......',
      args: [ '0xd335.....' ],
      transaction: {
        data: '0x70a08231000000000000000000000000d3355659195b93c.....',
        to: '0x8C4B6E......',
        from: '0xC0e......'
      }
    }

However transfer works (no error):

  `let a = await contractFYX.transfer(to, ethers.utils.parseEther(`${amount}`)); //<<== works!`

Here is a portion of output of contractFYX which seems normal:

contract FYX :  Contract {
      interface: Interface {
        fragments: [
          [ConstructorFragment],
          [EventFragment],
          [EventFragment],
          [FunctionFragment],
          [FunctionFragment],
          [FunctionFragment],
          [FunctionFragment],
          [FunctionFragment],
          [FunctionFragment],
          [FunctionFragment],
          [FunctionFragment],
          [FunctionFragment],
          [FunctionFragment],
          [FunctionFragment]
        ],
        _abiCoder: AbiCoder { coerceFunc: null },
        functions: {
          'allowance(address,address)': [FunctionFragment],
          'approve(address,uint256)': [FunctionFragment],
          'balanceOf(address)': [FunctionFragment],
          'decimals()': [FunctionFragment],
          'decreaseAllowance(address,uint256)': [FunctionFragment],
          'increaseAllowance(address,uint256)': [FunctionFragment],
          'name()': [FunctionFragment],
          'symbol()': [FunctionFragment],
          'totalSupply()': [FunctionFragment],
          'transfer(address,uint256)': [FunctionFragment],
          'transferFrom(address,address,uint256)': [FunctionFragment]
        },
        errors: {},
        events: {

the following provider.getBlockNumber returns current number of blocks:

//test connection
              provider.getBlockNumber().then(res => {
                console.log("blockNumber returned : ", res);  //<<==valid block# returned
              }).catch(error => console.log("Connection mainchain error ", error));

Didn't find anything suspicious in node log file. And output is 0x from provider.getCode(AddressOfcontractFYX):

 ` provider.getCode(fxydeployAddress) :  0x`

Shall getCode output the contract functions' code? What is the cause of this CALL_EXCEPTION for balanceOf?

[ricmoo]

If the code is 0x, it means your code isn’t deployed. If you are deploying it just before calling your function, you need to wait for the deployment to complete, for example in a test case.

I’ve also seen similar situation where the artifact files were not updated correctly.

[emclab]

Hi ricmoo, the contract was deployed a few days ago. I was puzzled since transferTo seems working. Shall I try to redeploy the contract?

[ricmoo]

Can you include the address? And double check on Etherscan?

[emclab]

re-deploy worked. It is on a private Besu network.

[emclab]

Re-deploy worked.