Looks like a bug in simulateContract.js

[HarmonyMind]

Hello!
I observe strange behavior in the simulateContract code.
I develop the application based on nextJS. Configuration from package.json:

"dependencies": {
"@rainbow-me/rainbowkit": "^2.1.0",
"@tanstack/react-query": "^5.37.1",
"abitype": "^1.0.2",
"next": "14.2.3",
"react": "^18",
"react-dom": "^18",
"usehooks-ts": "^3.1.0",
"viem": "^2.11.0",
"wagmi": "^2.9.2"
},
"devDependencies": {
"@types/node": "^20",
"@types/react": "^18",
"@types/react-dom": "^18",
"postcss": "^8",
"tailwindcss": "^3.4.1",
"typescript": "^5"
}

Next, the code that calls the smart contract (USDT smart-contract).

The goal is to get approval to transfer from one wallet to another and make this transfer.

const _abi = [
{
type: 'function',
name: 'approve',
stateMutability: 'nonpayable',
inputs: [
{ name: 'spender', type: 'address' },
{ name: 'amount', type: 'uint256' },
],
outputs: [{ type: 'bool' }],
},
{
type: 'function',
name: 'transferFrom',
stateMutability: 'nonpayable',
inputs: [
{ name: 'sender', type: 'address' },
{ name: 'recipient', type: 'address' },
{ name: 'amount', type: 'uint256' },
],
outputs: [{ type: 'bool' }],
},

]

let txnId = await writeContractAsync({
abi: _abi as Abi,
address: tokenAddress as Address, /// USDT contract address 
functionName: 'approve',
args: [
address as Address,
parseUnits(process.env.PRICE!, 6),],
chainId: chainId,
});

console.log('approve txn_id = ' + txnId as string);

App behavior on the Polygon network:

Metamask confirmation window appears and the expected entry is printed in the browser console:

approve txn_id = 0x4957fa50af02b0aa3df9d2b18fcd5d9f5784bf6257392a7ec1cbab5a3a78adf0

App behavior on the Arbitrum network:

on the Arbitrum network the Metamask window does not open, and in the browser console there is an entry:

TypeError: Cannot use 'in' operator to search for 'data' in 1103
at eval (getContractError.js:18:40)
at walk (base.js:78:13)
at walk (base.js:81:16)
at walk (base.js:81:16)
at CallExecutionError.walk (base.js:74:16)
at getContractError (getContractError.js:18:19)
at simulateContract (simulateContract.js:83:98)
at async simulateContract (simulateContract.js:30:33)
at async writeContract (writeContract.js:32:46)

Judging by the stack trace, the error occurs in the simulateContract code (simulateContract.js:83:98)

Here is the viem library code which is available in debug mode:

async function simulateContract(client, parameters) {
    const {abi, address, args, dataSuffix, functionName, ...callRequest} = parameters;
    const account = callRequest.account ? (0,
    _accounts_utils_parseAccount_js__WEBPACK_IMPORTED_MODULE_0__.parseAccount)(callRequest.account) : client.account;
    const calldata = (0,
    _utils_abi_encodeFunctionData_js__WEBPACK_IMPORTED_MODULE_1__.encodeFunctionData)({
        abi,
        args,
        functionName
    });
    try {
        const {data} = await (0,
        _utils_getAction_js__WEBPACK_IMPORTED_MODULE_2__.getAction)(client, _call_js__WEBPACK_IMPORTED_MODULE_3__.call, 'call')({
            batch: false,
            data: `${calldata}${dataSuffix ? dataSuffix.replace('0x', '') : ''}`,
            to: address,
            ...callRequest,
            account,
        });
        const result = (0,
        _utils_abi_decodeFunctionResult_js__WEBPACK_IMPORTED_MODULE_4__.decodeFunctionResult)({
            abi,
            args,
            functionName,
            data: data || '0x',
        });
        const minimizedAbi = abi.filter((abiItem)=>'name'in abiItem && abiItem.name === parameters.functionName);
        return {
            result,
            request: {
                abi: minimizedAbi,
                address,
                args,
                dataSuffix,
                functionName,
                ...callRequest,
                account,
            },
        };
    } catch (error) {
        throw (0,
        _utils_errors_getContractError_js__WEBPACK_IMPORTED_MODULE_5__.getContractError)(error, {
            abi,
            address,
            args,
            docsPath: '/docs/contract/simulateContract',
            functionName,
            sender: account?.address,
        });
    }
}

Question.

Why does this the same viem code run without errors on the Polygon network, but crash on the Arbitrum network?

[HarmonyMind]

Update on this issue.
I found out the reason for this error.
The reason is that either the wrong address of the ERC20 token was specified, or that the Token Decimals value for this token was specified incorrectly.
In these cases, the viem library produces such strange messages.
Sorry, for disturbing