Metamask-snap-account-abstraction-keyring eth_patchUserOperation isn't being invoked by core wallet

[voidash]

I’m working with the MetaMask Snap for Account Abstraction Keyring
https://github.com/MetaMask/snap-account-abstraction-keyring/tree/main.
Version : 0.4.2

So following the docs : https://docs.metamask.io/snaps/features/custom-evm-accounts/#account-abstraction-erc-4337 which describes the following methods and diagram shows these methods are called in sequence:
eth_prepareUserOperation: Returns a pseudo userOp that we will use to estimate the fee
eth_decodeUserOperationCallData: Used by the UI to decode the call data to display it to the user
eth_patchUserOperation: Snap can change some of the properties of the userOp before we ask the Snap to sign it
eth_signUserOperation: The Snap actually sign the user op

So in my dapp when i call something like

  async function sendTx() {
    console.log(acc);
    try {
      await window.ethereum.request({
       "method": "eth_sendTransaction",
       "params": [
        {
          from: "0xDd465B1000A102aeF17C6AF7C9C6DC251C735B00", // my snap address
          to: "0x303d09061E4B92DaE830F52Ff3Bb59cd9c0CD79f",
          value: "0x18832323232223",
          data: "0x",
        }
      ],
      });
    } catch(err) {
      console.log(`Error encountered ${err}`);
    }
  }

I can see that eth_prepareuserOperation is being called but then it errors out with

"Error: local:http://localhost:8093 failed to respond to the request in time.
at a (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/background-2.js:1:269776)
at async h.submitRequest (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/common-2.js:1:118149)
at async H.g (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/background-1.js:1:67090)
at async H.f (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/background-1.js:1:66384)
at async H.patchUserOperation (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/background-1.js:1:63265)
at async de.patchUserOperation (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/common-2.js:1:208634)
at async n.SnapSmartContractAccount.updateUserOperation (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/background-2.js:1:510066)
at async J.d (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/background-2.js:1:496938)
at async J.o (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/background-2.js:1:494352)
at async chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/background-2.js:1:493942
at async w (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/background-2.js:1:494069)
at async transactionHash (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/background-2.js:1:494123)
at async n.addDappTransaction (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/background-0.js:1:107807)
at async chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/common-1.js:1:1072019
at async chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/common-2.js:1:55783"

Looking at the diagram again this fails at

To reproduce my error, Here are more details

• Metamask snap version: 12.10.1-flask.0
• (snap and site, no changes) metamask-snap-keyring-api : https://github.com/MetaMask/snap-account-abstraction-keyring/releases/tag/v0.4.2
• Network : Anvil local (chain ID: 31337)
• Bundler used: https://github.com/alchemyplatform/rundler modified dev to have chain ID: 31337

Entrypoint contract : v0.6.0 (0x5FF137D4b0FDCD49DcA30c7CF57E578a026d2789)
SimpleAccountFactory also hasn't been modified and is deployed as is

Rundler(bundler) is being run as

RUST_LOG=info cargo run -- node --network dev \
  --node_http http://localhost:8545 --builder.private_keys 0x5de4111afa1a4b94908f83103eb1f1706367c2e68ca870fc3fb9a804cdab365a,0x5de4111afa1a4b94908f83103eb1f1706367c2e68ca870fc3fb9a804cdab365a --rpc.api eth,debug --unsafe --builder.max_bundle_size 1 --user_operation_event_block_distance 10000 --metrics.port 9000 --rpc.corsdomain "*"

[ccharly]

hello @voidash

Could you please try to use the version 0.5.0 instead?

• https://github.com/MetaMask/snap-account-abstraction-keyring/releases/tag/v0.5.0

We added a new requirement for KeyringAccount now that requires a new scopes field. Basically, that's an array of "scopes" (CAIP-2 chain ID) that the account "supports".

We now use this information to know which chains are supported by your account.

In your specific case of using 4337 with the Anvil network, the scope would be eip155:31337 (which matches the error message you get).

Before diving a bit more into your repro, could you try using version 0.5.0 instead and let me know how this goes with this version?

Thanks!

[voidash]

I have created a issue regarding not being able to use v0.5.0 yesterday

MetaMask/snap-account-abstraction-keyring#170

[voidash]

I have updated the error in the discussion description itself. But here is the exact error

Error: local:http://localhost:8093 failed to respond to the request in time.
at a (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/background-2.js:1:269776)
at async h.submitRequest (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/common-2.js:1:118149)
at async H.g (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/background-1.js:1:67090)
at async H.f (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/background-1.js:1:66384)
at async H.patchUserOperation (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/background-1.js:1:63265)
at async de.patchUserOperation (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/common-2.js:1:208634)
at async n.SnapSmartContractAccount.updateUserOperation (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/background-2.js:1:510066)
at async J.d (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/background-2.js:1:496938)
at async J.o (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/background-2.js:1:494352)
at async chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/background-2.js:1:493942
at async w (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/background-2.js:1:494069)
at async transactionHash (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/background-2.js:1:494123)
at async n.addDappTransaction (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/background-0.js:1:107807)
at async chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/common-1.js:1:1072019
at async chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/common-2.js:1:55783"

guess i copied the wrong error last time ... sorry

[ccharly]

No worries at all!

This "feature" is really new and has not been released yet (on the extension side I mean).

Here's the PR that introduced that change:

• feat: add scopes field to KeyringAccount metamask-extension#29195

I saw you were using this version of Flask: 12.10.1-flask.0, do you mind testing on the extension mainline directly for now (or at least, a more recent version, see below)?. I just want to make sure you are not getting any error down the line that would be caused by other internal packages (this feature involves some internal breaking changes).

Could you try using that build first:

• feat: add scopes field to KeyringAccount metamask-extension#29195 (comment)
  • Pick the builds (flask) chrome, firefox
  • Download the "chrome" version
• Then you can follow those instructions to load your custom build.

I will try to repro this with your setup if you are still facing the same error. Let me know how this goes!

Thanks 😄

[roo-shy]

Referencing MetaMask/snap-account-abstraction-keyring#170