Error: Exceeded maximum duration (50 sec) waiting to get receipt for userOpHash 0xf3d089664e2ff8713e98968ea695cb2aaf0143ac025203f6b2e85cc737b76e9e. Try getting the receipt manually using eth_getUserOperationReceipt rpc method on bundler ❯ Timeout.<anonymous> src/bundler/Bundler.ts:211:17

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:81:10 ❯ Module.sendRequest src/account/utils/HttpRequests.ts:49:11 ❯ Bundler.sendUserOp src/bundler/Bundler.ts:157:59 ❯ BiconomySmartAccountV2.sendSignedUserOp src/account/BiconomySmartAccountV2.ts:1259:29 ❯ BiconomySmartAccountV2.sendUserOp src/account/BiconomySmartAccountV2.ts:1222:29 ❯ tests/modules/write.test.ts:825:29 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ 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>' }

AccountAbstractionError: InvalidSmartAccountNonceError aa25: The smart account sender nonce is invalid. Potential cause(s): Your nonce is invalid. The user operation may be re-using an old nonce, or formatted the nonce incorrectly. the userOp is not 1 more than the nonce in the nonceSequenceNumber map on the EntryPoint You have sent two userOps with same nonce with very little time difference, both pass simulation as both are at the time of simulation are valid. Whichever userOp lands on chain first will make the second userOp's nonce invalid You have not waited for a previous userOp to be confirmed the RPC passed into the SDK is using a free tier, which won't have the same performance and slow state data propagation as a paid RPC. You have sent a userOp to an incorrect chain Potential solution(s): Verify that you are using the correct nonce for the user operation. The nonce should be the current nonce of the smart account for the selected key. Consider using functions like getAccountNonce Wait for transaction confirmation before firing a second tx If you are trying parallel transactions execution, refer to 2d nonces (nonceOptions) here: (https://docs.biconomy.io/Account/methods#builduserop) for more details Pay for a tierd RPC provider. Verify that the nonce is formatted correctly. Details: "Error coming from Bundler: AA25 invalid account nonce" Version: viem@2.9.16 ❯ Module.getAAError src/bundler/utils/getAAError.ts:81:10 ❯ Module.sendRequest src/account/utils/HttpRequests.ts:49:11 ❯ Bundler.sendUserOp src/bundler/Bundler.ts:157:59 ❯ BiconomySmartAccountV2.sendSignedUserOp src/account/BiconomySmartAccountV2.ts:1259:29 ❯ BiconomySmartAccountV2.sendUserOp src/account/BiconomySmartAccountV2.ts:1222:29 ❯ tests/paymaster/write.test.ts:89:22 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: '"Error coming from Bundler: AA25 invalid account nonce"', docsPath: undefined, metaMessages: [ 'aa25: The smart account sender nonce is invalid.\n', 'Potential cause(s): \n\nYour nonce is invalid.\nThe user operation may be re-using an old nonce, or formatted the nonce incorrectly.\nthe userOp is not 1 more than the nonce in the nonceSequenceNumber map on the EntryPoint\nYou have sent two userOps with same nonce with very little time difference, both pass simulation as both are at the time of simulation are valid. Whichever userOp lands on chain first will make the second userOp\'s nonce invalid\nYou have not waited for a previous userOp to be confirmed\nthe RPC passed into the SDK is using a free tier, which won\'t have the same performance and slow state data propagation as a paid RPC.\nYou have sent a userOp to an incorrect chain\n', 'Potential solution(s): \n\nVerify that you are using the correct nonce for the user operation. The nonce should be the current nonce of the smart account for the selected key. Consider using functions like getAccountNonce\nWait for transaction confirmation before firing a second tx\nIf you are trying parallel transactions execution, refer to 2d nonces (nonceOptions) here: (https://docs.biconomy.io/Account/methods#builduserop) for more details\nPay for a tierd RPC provider.\nVerify that the nonce is formatted correctly.' ], shortMessage: 'InvalidSmartAccountNonceError', version: '@biconomy/account@4.2.0', walk: 'Function<walk>' }

AssertionError: expected 0n to be 1n // Object.is equality - Expected + Received - 1n + 0n ❯ tests/paymaster/write.test.ts:254:50

AssertionError: expected 7970288988196201762n to be 0n // Object.is equality - Expected + Received - 0n + 7970288988196201762n ❯ tests/paymaster/write.test.ts:289:30

Process completed with exit code 1.