Only one account is listed by the configured Web3Provider

[balteo]

Hello,

I am trying to configure ethers.js together with metamask.

Here is how I configure my provider:

  initProvider() {
    const ethereum = window['ethereum'];
    ethereum.enable();
    this.provider = new ethers.providers.Web3Provider(ethereum);//Metamask is used but only one account is listed...
  }

I have Ganache running with a number of accounts. However, when I try to retrieve/list the accounts like so: this.provider.listAccounts(), I only get one element in the array...

Note that I can see all accounts when I use the following configuration for my provider:

const provider = new ethers.providers.JsonRpcProvider(url);//Metamask is left out but I can list all accounts.

However, I need both metamask and the full list of accounts. What am I getting wrong? Do I need two separate providers? Note that metamask itself lists all Ganache accounts properly.

Can someone please help?

[zemse]

Metmask now requires user to connect specific accounts to the dapp during first time, for privacy purposes. Ganache is pretty much a dev tool so it is allowing access to all the available accounts.

window.ethereum.request({
    method: "wallet_requestPermissions",
    params: [
      {
        eth_accounts: {}
      }
    ]
  });

The above will trigger the metamask popup again and user can tick multiple accounts to give access to the dapp.

[balteo]

Thanks a lot @zemse

I have issued a wallet_requestPermissions request followed by a eth_requestAccounts request. I do see the 3 selected accounts in the response from the wallet_requestPermissions request but they are located in a deeply nested property called caveat. However, when I subsequently issue the eth_requestAccounts I only see the first account..

What I am getting wrong?

Here is the result from the first request:

[sash20m]

Same thing here. But I think it's ok what @zemse said. When the user loads the website for the first type, the window to select all his addresses pups up, and then you take them from caveats and just store them in memory. Now you can just show them to the screen. If you want to make a functionality for the user to switch between addresses, you just call the eth_requestAccounts when he clicks on a new address and that will give you the current active account that the user would like to use. I am not sure if that solves your problem but for the functionality of the switching account, the data you get is enough.