AccountAbstractionError: SmartAccountValidationRevertedError aa23: The smart account sender reverted or ran out of gas during the validation of the user operation. Potential cause(s): Your smart account is out of gas. Potential solution(s): Make sure the signature verification logic of the smart account is implemented correctly. Ensure you are using the same signer, you created the account with. Verify that the verificationGasLimit is high enough to cover the validateUserOp function's gas costs. Make sure validateUserOp returns uint(1) for invalid signatures, and MUST NOT REVERT when the signature is invalid If you are using paymaster to sponsor the transactions, ensure that the paymasterAndData field of the user operation is correctly set to enable proper handling of gas fees Check that you have enough balance at the paymaster. If you are not using a paymaster, verify that the sender address has enough native tokens to cover the required pre fund. Verify that the validateUserOp function is implemented with the correct logic, and that the user operation is supposed to be valid. If the error persists, try simulating validateUserOp method on entrypoint contract with the user operation using tenderly Details: "Error coming from Paymaster: AA23 reverted (or OOG)" Version: viem@2.9.16 ❯ Module.getAAError src/bundler/utils/getAAError.ts:80:10 ❯ Module.sendRequest src/account/utils/HttpRequests.ts:46:11 ❯ BiconomyPaymaster.getPaymasterAndData src/paymaster/BiconomyPaymaster.ts:341:41 ❯ BiconomySmartAccountV2.getPaymasterAndData src/account/BiconomySmartAccountV2.ts:1018:27 ❯ BiconomySmartAccountV2.buildUserOp src/account/BiconomySmartAccountV2.ts:1675:16 ❯ tests/modules/write.test.ts:338:20 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: '"Error coming from Paymaster: AA23 reverted (or OOG)"', docsPath: undefined, metaMessages: [ 'aa23: The smart account sender reverted or ran out of gas during the validation of the user operation.\n', 'Potential cause(s): \n\nYour smart account is out of gas.\n', 'Potential solution(s): \n\nMake sure the signature verification logic of the smart account is implemented correctly.\nEnsure you are using the same signer, you created the account with.\nVerify that the verificationGasLimit is high enough to cover the validateUserOp function\'s gas costs.\nMake sure validateUserOp returns uint(1) for invalid signatures, and MUST NOT REVERT when the signature is invalid\nIf you are using paymaster to sponsor the transactions, ensure that the paymasterAndData field of the user operation is correctly set to enable proper handling of gas fees\nCheck that you have enough balance at the paymaster.\nIf you are not using a paymaster, verify that the sender address has enough native tokens to cover the required pre fund.\nVerify that the validateUserOp function is implemented with the correct logic, and that the user operation is supposed to be valid.\nIf the error persists, try simulating validateUserOp method on entrypoint contract with the user operation using tenderly' ], shortMessage: 'SmartAccountValidationRevertedError', version: '@biconomy/account@4.2.0', walk: 'Function<walk>' }

AccountAbstractionError: InvalidSmartAccountSignatureError aa24: The smart account sender signature is invalid. Potential cause(s): The signature field of userOp is inaccurate. The userOp field is altered after the userOp has been signed. Potential solution(s): Make sure you have selected the correct chainId and entryPointAddress when computing the userOpHash. Make sure you have selected the correct corresponding bundler URL when computing the userOpHash. Verify that the user operation was correctly signed, and that the signature was correctly encoded in the signature field of the user operation. Most smart account implementations sign over the userOpHash. Make sure that the userOpHash is correctly computed. Consider leveraging functions like getUserOperationHash. Make sure the smart account signature verification function is correctly implemented. Details: "Error coming from Bundler: AA24 signature error" Version: viem@2.9.16 ❯ Module.getAAError src/bundler/utils/getAAError.ts:80:10 ❯ Module.sendRequest src/account/utils/HttpRequests.ts:46:17 ❯ Bundler.sendUserOp src/bundler/Bundler.ts:157:59 ❯ BiconomySmartAccountV2.sendSignedUserOp src/account/BiconomySmartAccountV2.ts:1253:29 ❯ BiconomySmartAccountV2.sendUserOp src/account/BiconomySmartAccountV2.ts:1216:29 ❯ tests/modules/write.test.ts:719:31 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: '"Error coming from Bundler: AA24 signature error"', docsPath: undefined, metaMessages: [ 'aa24: The smart account sender signature is invalid.\n', 'Potential cause(s): \n\nThe signature field of userOp is inaccurate.\nThe userOp field is altered after the userOp has been signed.\n', 'Potential solution(s): \n\nMake sure you have selected the correct chainId and entryPointAddress when computing the userOpHash.\nMake sure you have selected the correct corresponding bundler URL when computing the userOpHash.\nVerify that the user operation was correctly signed, and that the signature was correctly encoded in the signature field of the user operation.\nMost smart account implementations sign over the userOpHash. Make sure that the userOpHash is correctly computed. Consider leveraging functions like getUserOperationHash.\nMake sure the smart account signature verification function is correctly implemented.' ], shortMessage: 'InvalidSmartAccountSignatureError', version: '@biconomy/account@4.2.0', walk: 'Function<walk>' }

Process completed with exit code 1.