We are sorry to cause any inconvenience while interacting with biconomy SDK. We are trying our best to send meaningful error messages that can help you do quick fixes without interacting with any support channel. Some of the error messages are not in our control as we are using some standard contract ( e.g EntryPoint ) to provider gasless experience. Following are some standard error messages that can help you apply quick fixes and sort the issues.
Ensure that you are using the bundler, paymaster, and RPC URL of the same blockchain.
|AA21 didn’t pay prefund
|Throws if your smart wallet does not have funds to send transaction. Send some native tokens in your smart wallet to be able to resolve the error.
|AA23 reverted (or OOG)
|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. If the error persists, try simulating
validateUserOp method on entrypoint contract with the user operation on tenderly. Also ensure, if sender has sufficient native tokens to cover the User Operation's gas costs. 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.
|AA10 sender already constructed
|Throws if your smart wallet is already created but you are still sending
initcode in userOp.
|AA13 initCode failed or OOG
|Throws if userOp doesn’t have enough
verificationGasLimit to create smart account. you need to increase
verificationGasLimit to be able to send transaction.
|AA14 initCode must return sender
|Throws if the factory contract that you are using to deploy smart account does not return smart account address. Or
sender field in userOp does not have same address as factory contract is creating for you.
|AA93 invalid paymasterAndData
paymasterAndData created by signing service is not valid.
|AA95 out of gas
verificationGasLimit is not correct for executing callData sent in userOp. Make sure
verificationGasLimit are not too high and use correct estimated values for preparing the userOp.
|AA90 invalid beneficiary
|Throws if the beneficiary address sent in userOp that is going to get sponsored transaction fee back is not valid.
|AA31 paymaster deposit too low
|Throws if the dApp you have created using dashboard does not have enough funds in its gas tank to sponsor transaction.
|AA41 too little verificationGas
|Throws if the userOp does not have enough
verificationGasLimit to create smart account. you need to increase
verificationGasLimit to be able to resolve this error.
|AA33 reverted (or OOG)
|Throws if the transaction you are sending is not valid or userOp does not have enough
verificationGasLimit to be able to validate transaction. Try increasing
verificationGasLimit or verify either the transaction you are making is valid to be able to resolve this error. In case of SPONSORED paymaster you might get this error due to insufficient token balance.
|AA40 over verificationGasLimit
|Throws when gas used in the verification step on chain, is more than the
verificationGasLimit. Try increasing the
verificationGasLimit value to be able to resolve this error.
|AA51 prefund below actualGasCost
|Throws because of 2 possible reasons: either your smart wallet does not have funds to send transaction or the dApp you have created using dashboard does not have enough funds in its gas tank to sponsor transaction.
|AA34 signature error
|Throws when the paymaster's signature is invalid. Check the format of the signature in paymasterAndData. Once the paymasterData is created, any changes to the userOp may lead to this error. In case you have passed the
calculateGasLimits flag as true while creating the paymasterData, do update the gasLimits as mentioned here to avoid this error.
|AA25 Invalid Account Nonce
|Throws when the nonce is invalid. The user operation may be re-using an old nonce, or formatted the nonce incorrectly. If you are trying parallel transactions execution, refer to nonceOptions in this page for more details
|No policies were set on the dashboard. Please set policies to allow gas sponsorship via paymasters
|Throws if the contracts are not whitelisted using the dashboard to be able to sponsor transactions.
|error in txn
|Throws when there is internal server error from relayer side which can be due to multiple reasons. In this we would require the transacitonId from the user.
|only allowed via delegateCall
|Throws when trying to send native tokens directly to the Smart Account implementation.
|Smart Account:: new Signatory address cannot be self
|Throws when trying to set the Smart Account address as its own owner.
|new Signatory address cannot be same as old one
|Throws when trying to set owner with an address that is already an owner.
|Address cannot be zero
|Throws when trying to update to a zero address as implementation.
|Throws when token Gas Price factor provided is 0.
|Invalid signatures length
|Throws when the length of the signature provided in the Forward flow is less than 65.
|Could not get network config values
|Throws when we can’t find the provided network in the network config.
|Throws at onlyEntryPoint when msg.sender is not an EntryPoint set for this Smart Account
|Throws if zero address has been provided as Fallback Handler address
|Throws if zero address has been provided as Entry Point address
|Throws at mixedAuth when msg.sender is not an owner neither _self
|Throws if transfer of tokens failed. Arguments: token address, receiver address, amount.
|Throws if trying to change an owner of a SmartAccount to the zero address
|Throws if zero address has been provided as Base Implementation address
|Throws if there is no code at implementationAddress
|Throws at onlyOwner when msg.sender is not an owner
|Throws at _requireFromEntryPointOrOwner when msg.sender is not an EntryPoint neither an owner
|Throws if trying to initialize a Smart Account that has already been initialized
|Throws if not enough gas is left at some point
|Throws if not able to estimate gas. It can happen when the amount of gas and its price are both zero and the transaction has failed to be executed
|Throws if contract signature is provided in the wrong format
|Throws when isValidSignature for the contract signature and data hash return differs from EIP1271 Magic Value
|Throws when the address that signed the data (restored from signature) differs from the expected signer
|Throws when the transaction execution fails
|Throws when trying to transfer to the zero address
|Throws when data for executeBatchCall provided in the wrong format (i.e. empty array or lengths mismatch)
|Throws when the Proxy (Smart Account) deployment attempt failed
|Throws when trying to initialize the module manager that has already been initialized
|Throws when a delegatecall during module manager initialization has failed
|Throws when address(0) or SENTINEL_MODULES constant has been provided as a module address
|Throws when trying to enable a module that has already been enabled
|Throws when the module and previous module mismatch
|Throws when trying to execute a transaction from a module that is not enabled
|Throws when the caller is not address(this)
|Throws when the Entry Point address provided is address(0)
|Throws when the verifying signer address provided is address(0)
|Throws when the paymaster Id address provided is address(0)
|Throws when 0 has been provided as the deposit amount
|Throws when trying to withdraw to address(0)
|Throws when trying to withdraw more than the available balance
|Throws when the signature provided to the paymaster has an invalid length