Invalid Transaction Key 5.3.1

[JR0210]

Describe the bug
When trying to sign, submit or populate a transaction. The transaction object seems to have "invalid keys". Tried updating my ethers.js version after finding previous reports of similar issues but no luck.

Error currently occurs on await wallet.populateTransaction(tx) but also occurs on await wallet.sendTransaction(unsignedTx)

Error Message:

Error: invalid transaction key: v (argument="transaction", value={"nonce":62,"gasPrice":{"type":"BigNumber","hex":"0x01a13b8600"},"gasLimit":{"type":"BigNumber","hex":"0x7918"},"to":"...","value":{"type":"BigNumber","hex":"0x00"},"data":"...","chainId":56,"v":147,"r":"...","s":"....","from":"...","hash":"...","type":null}, code=INVALID_ARGUMENT, version=abstract-signer/5.3.0

Unsure if I'm doing anything incorrectly or if this is a genuine issue?

Reproduction steps
Running Node locally connecting to BSC through Quicknode websocket.
Using the WebSocketProvider.

async () => {
  await provider.ready;
  const wallet = new ethers.Wallet(privatekey, provider);
  const account = wallet.connect(provider);

  const factory = new ethers.Contract(
    addresses.PANCAKESWAP_FACTORY_ADDR_V2,
    pancakeswapFactoryAbi,
    account
  );
  
  const router = new ethers.Contract(
    addresses.PANCAKESWAP_ROUTER_ADDR_V2,
    pancakeswapRouterAbi,
    account
  );
  const tokenIn = data.WBNB;
  const tokenOut = data.to_PURCHASE;
  const tokenContract = new ethers.Contract(data.to_PURCHASE, BEP20, account);
  const pair = new ethers.Contract(pairAddress, pancakeswapPairAbi, account);

  // Buy x amount of the new token with wBNB
  const amountIn = ethers.utils.parseUnits(`${data.AMOUNT_OF_WBNB}`, 'ether');

  const amounts = await router.getAmountsOut(amountIn, [tokenIn, tokenOut]);
 
  const amountOutMin = amounts[1].sub(amounts[1].div(`${data.Slippage}`)); 
 
  const tx = await router.swapExactTokensForTokens(
      amountIn,
      amountOutMin,
      [tokenIn, tokenOut],
      data.recipient,
      Date.now() + 1000 * 60 * 2, // 2 minutes
      {
        'gasLimit': data.gasLimit,
        'gasPrice': ethers.utils.parseUnits(`${data.gasPrice}`, 'gwei')
      }
    );

  console.log(tx, 'tx');
  const unsignedTx = await wallet.populateTransaction(tx)

  console.log(getMethods(signer), 'signer')
  // console.log(signer.checkTransaction(tx), 'tx');
  const signedTx = await wallet.sendTransaction(unsignedTx)
  const receipt = await signedTx.wait(); 
}

[ricmoo]

Your router is connected to account, so that call to router.swapExactTokensForToke s is sending the transaction. Which means the transaction you are getting back is signed and sent to the network. It is too late to try populating it by then.

If you are trying to manually control that, you can use router.populateTransaction.swapExactTokensForTokens. Or you can just pass your wallet into the router directly and skip all the manual work.

Make sense? (moving to discussions)

[ricmoo]

Here are the docs regarding calling a write method on a contract:

https://docs.ethers.io/v5/api/contract/contract/#Contract--write

[JR0210]

Ah thank you, I understand. Apologies, new to ETH dev. The transaction doesn't ever seem to complete so it's stuck on await tx.wait() otherwise. Is this likely just linked to the gas limit/price? I have tried to increase both with no luck unless I increase them drastically, to the point my wallet doesn't have enough to cover the fee.

[ricmoo]

The gas limit should bot need any adjustment, especially if you let ethers estimate it for you (by omitting it). What gas price is it using? The automatic values for that should also work fine. Do you see the tx in Etherscan? It should still show up.