AssertionError: expected 2n to be 1n // Object.is equality - Expected + Received - 1n + 2n ❯ tests/account/write.test.ts:276:34

AssertionError: expected 7980529751172713212n to deeply equal 7980808554646285413n - Expected + Received - 7980808554646285413n + 7980529751172713212n ❯ tests/account/write.test.ts:323:32

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: AA25 invalid account nonce" Version: [email protected] ❯ Module.getAAError src/bundler/utils/getAAError.ts:81:10 ❯ Module.sendRequest src/account/utils/HttpRequests.ts:46:11 ❯ Bundler.estimateUserOpGas src/bundler/Bundler.ts:110:49 ❯ BiconomySmartAccountV2.estimateUserOpGas src/account/BiconomySmartAccountV2.ts:1297:9 ❯ BiconomySmartAccountV2.buildUserOp src/account/BiconomySmartAccountV2.ts:1621:18 ❯ tests/account/write.test.ts:457:34 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ 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.\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>' }

AssertionError: expected '0xFA66E705cf2582cF56528386Bb9dFCA1197…' not to be '0xFA66E705cf2582cF56528386Bb9dFCA1197…' // Object.is equality ❯ tests/account/write.test.ts:556:34

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: AA25 invalid account nonce" Version: [email protected] ❯ Module.getAAError src/bundler/utils/getAAError.ts:81:10 ❯ Module.sendRequest src/account/utils/HttpRequests.ts:46:17 ❯ 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/account/write.test.ts:587:24 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ 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.\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>' }

AssertionError: promise resolved "{ …(3) }" instead of rejecting - Expected + Received - [Error: rejected promise] + Object { + "userOpHash": "0x9ffed4fd3dd489ee19c3f8e3ec02150528d3636d70535cfa88e185b746679e85", + "wait": [Function wait], + "waitForTxHash": [Function waitForTxHash], + } ❯ tests/account/write.test.ts:613:7

AssertionError: expected '0xFA66E705cf2582cF56528386Bb9dFCA1197…' to be '0x3079B249DFDE4692D7844aA261f8cf7D927…' // Object.is equality - Expected + Received - 0x3079B249DFDE4692D7844aA261f8cf7D927A0DA5 + 0xFA66E705cf2582cF56528386Bb9dFCA119767262 ❯ tests/account/write.test.ts:634:30

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: [email protected] ❯ Module.getAAError src/bundler/utils/getAAError.ts:81:10 ❯ Module.sendRequest src/account/utils/HttpRequests.ts:46: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:827: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/[email protected]', walk: 'Function<walk>' }

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

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