Add an integration with azero-wallet snap

[piotr-roslaniec]

• Based on r-8.7
• Merged changes up to r-9.1
• Adds integration with azero-wallet snap. Uses said snap as a new signer.

[jalooc]

So far looks good. It's a draft PR, so I imagine there are some more change coming? (hence not approving yet)

[jalooc]

Oh, I also asked @Marcin-Radecki @youPickItUp to co-review, because he's more up-to-date with this project.

[youPickItUp]

Looks good! I had problem testing 😅 How can I test whole flow with snap? I get

[piotr-roslaniec]

Hi @youPickItUp. Until this snap registry PR is merged, you have to use the "Flask" development build of MetaMask

[youPickItUp]

Sorry, again couldn't get it to work 😢
Probably need some assistance 🙏
More in comment

[youPickItUp]

Hello! I'm sorry for the delay. I wanted to deploy your change on our stage, but before, I've re-tested it and I'm afraid it's not working 😬 Perhaps I mess edsomething up, but it seems to hang on snap.connect() indefinitely. Could you assist me?

[piotr-roslaniec]

@youPickItUp Let's see if we can debug this remotely. Could you provide me with some extra information about your extension? You can find them in the Extension details view in Google Chrome (Mozilla Firefox has analogous section):

The background.html file contains a process used by the extension. You can find more information about the extension there. This is how the console looks like upon successful snap.connect():

[youPickItUp]

I don't see any change in the background.html console when I click the connect, some errors appear when I open the extension, but don't seem dangerous 🤷

The window.ethereum.isMetaMask is set to true.

I don't have the snap installed yet.

[youPickItUp]

I figured it out - I had Encrypt extension that somehow interfered with sending message to MetaMask 🤯
Sorry for inconvenience 😅

[youPickItUp]

Could you look into Enkrypt blocking Metamask integration issue? I'm a bit afraid this could be a somewhat common issue 😅

[piotr-roslaniec]

@youPickItUp I'm afraid it's another variation of a classic "browser wallets fighting over the monopoly of window.ethereum" problem. I will look into it - The least I can do is throw an error and ask the user to reconnect their wallet.