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. 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 leveraging functions like getAccountNonce. Verify that the nonce is formatted correctly. If you are trying parallel transactions execution, refer to nonceOptions here: (https://docs.biconomy.io/Account/methods#builduserop) for more details Details: "Error coming from Paymaster: UserOperation reverted during simulation with reason: AA25 invalid account nonce" Version: [email protected] ❯ 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:1015:27 ❯ BiconomySmartAccountV2.buildUserOp src/account/BiconomySmartAccountV2.ts:1516:16 ❯ BiconomySmartAccountV2.sendTransaction src/account/BiconomySmartAccountV2.ts:1410:20 ❯ tests/account/write.test.ts:204:22 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: '"Error coming from Paymaster: UserOperation reverted during simulation with reason: 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.\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 leveraging functions like getAccountNonce.\nVerify that the nonce is formatted correctly.\nIf you are trying parallel transactions execution, refer to nonceOptions here: (https://docs.biconomy.io/Account/methods#builduserop) for more details' ], shortMessage: 'InvalidSmartAccountNonceError', version: '@biconomy/[email protected]', 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. 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 leveraging functions like getAccountNonce. Verify that the nonce is formatted correctly. If you are trying parallel transactions execution, refer to nonceOptions here: (https://docs.biconomy.io/Account/methods#builduserop) for more details Details: "Error coming from Bundler: UserOperation reverted during simulation with reason: AA25 invalid account nonce" Version: [email protected] ❯ Module.getAAError src/bundler/utils/getAAError.ts:80:10 ❯ Module.sendRequest src/account/utils/HttpRequests.ts:46:17 ❯ Bundler.estimateUserOpGas src/bundler/Bundler.ts:110:49 ❯ BiconomySmartAccountV2.estimateUserOpGas src/account/BiconomySmartAccountV2.ts:1288:9 ❯ BiconomySmartAccountV2.buildUserOp src/account/BiconomySmartAccountV2.ts:1522:14 ❯ BiconomySmartAccountV2.getTokenFees src/account/BiconomySmartAccountV2.ts:1093:20 ❯ tests/paymaster/read.test.ts:88:33 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: '"Error coming from Bundler: UserOperation reverted during simulation with reason: 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.\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 leveraging functions like getAccountNonce.\nVerify that the nonce is formatted correctly.\nIf you are trying parallel transactions execution, refer to nonceOptions here: (https://docs.biconomy.io/Account/methods#builduserop) for more details' ], shortMessage: 'InvalidSmartAccountNonceError', version: '@biconomy/[email protected]', 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. 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 leveraging functions like getAccountNonce. Verify that the nonce is formatted correctly. If you are trying parallel transactions execution, refer to nonceOptions here: (https://docs.biconomy.io/Account/methods#builduserop) for more details Details: "Error coming from Paymaster: AA25 invalid account nonce" Version: [email protected] ❯ Module.getAAError src/bundler/utils/getAAError.ts:80:10 ❯ Module.sendRequest src/account/utils/HttpRequests.ts:46:17 ❯ BiconomyPaymaster.getPaymasterFeeQuotesOrData src/paymaster/BiconomyPaymaster.ts:204:41 ❯ BiconomySmartAccountV2.getSupportedTokens src/account/BiconomySmartAccountV2.ts:1134:31 ❯ tests/paymaster/read.test.ts:99:22 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: '"Error coming from Paymaster: 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.\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 leveraging functions like getAccountNonce.\nVerify that the nonce is formatted correctly.\nIf you are trying parallel transactions execution, refer to nonceOptions here: (https://docs.biconomy.io/Account/methods#builduserop) for more details' ], shortMessage: 'InvalidSmartAccountNonceError', version: '@biconomy/[email protected]', 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. 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 leveraging functions like getAccountNonce. Verify that the nonce is formatted correctly. If you are trying parallel transactions execution, refer to nonceOptions here: (https://docs.biconomy.io/Account/methods#builduserop) for more details Details: "Error coming from Bundler: UserOperation reverted during simulation with reason: AA25 invalid account nonce" Version: [email protected] ❯ Module.getAAError src/bundler/utils/getAAError.ts:80:10 ❯ Module.sendRequest src/account/utils/HttpRequests.ts:46:11 ❯ Bundler.estimateUserOpGas src/bundler/Bundler.ts:110:49 ❯ BiconomySmartAccountV2.estimateUserOpGas src/account/BiconomySmartAccountV2.ts:1288:9 ❯ BiconomySmartAccountV2.buildUserOp src/account/BiconomySmartAccountV2.ts:1522:14 ❯ BiconomySmartAccountV2.getTokenFees src/account/BiconomySmartAccountV2.ts:1093:20 ❯ tests/paymaster/read.test.ts:127:9 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: '"Error coming from Bundler: UserOperation reverted during simulation with reason: 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.\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 leveraging functions like getAccountNonce.\nVerify that the nonce is formatted correctly.\nIf you are trying parallel transactions execution, refer to nonceOptions here: (https://docs.biconomy.io/Account/methods#builduserop) for more details' ], shortMessage: 'InvalidSmartAccountNonceError', version: '@biconomy/[email protected]', walk: 'Function<walk>' }

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

Process completed with exit code 1.