MetaMask: 'eth_accounts' unexpectedly updated accounts

[xmaysonnave]

Metamask Mobile v0.2.19 (32)

Describe the bug

Unable to receive the selected eth_accounts once the user confirmed the current account on Metamask Mobile.

I started to remote debug the app and got the following exception :

MetaMask: 'eth_accounts' unexpectedly updated accounts. Please report this bug.

This app is working with Metamask extension on Chrome an used to work with Metamask Mobile.

Here the logic implemented :

      // https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1102.md
      await provider.request({ method: 'eth_requestAccounts' })
      // https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1193.md
      accounts = await provider.request({ method: 'eth_accounts' })
      if (
        accounts === undefined ||
        accounts == null ||
        Array.isArray(accounts) === false ||
        accounts.length === 0
      ) {
        throw new Error('Unable to retrieve any Ethereum accounts...')
      }

The eth_requestAccounts triggers the UI. UX 'Connect to this site ?' Confirmed.
The eth_accounts generate the mentioned exception and the DApp receives an empty array.

Expected behavior
The eth_accounts call should send an array who contains the selected account.

Smartphone (please complete the following information):

• Device: Redmi Note 7 Pro
• OS: MIUI 11
• Version 11.0.9.0

Thanks

---

to be added after bug submission by internal support / PM
Severity

• How critical is the impact of this bug on a user?
• Add stats if available on % of customers impacted
• Is this visible to all users?
• Is this tech debt?

[rickycodes]

@xmaysonnave I can't seem to reproduce this and I am wondering if it's still an issue for you? It's true that accounts = await ethereum.request({ method: 'eth_accounts' }) returns and empty array if the user hasn't connected to the dapp, but it seems to work fine once I am connected?:

> accounts = await ethereum.request({ method: 'eth_accounts' })
<- ["0xc7d3bfd..."]

this was on android, i also tested via our dapp which using the same methods here: https://metamask.github.io/test-dapp/

[xmaysonnave]

@rickycodes Thanks for your feedback.
Here is to reproduce the error.
Clear your privacy data.
1 - await provider.request({method:'requestAccounts'})
The UI popup to connect the Dapp to the current account
2 - await provider.request({method:'eth_accounts'})
No errors, but return an empty array
3 - Once this problems occured I tested with an await provider.enable()
The UI popup a second time to connect the Dapp
No errors and enable returns a populated array.

[AlexJupiter]

@xmaysonnave I'm going to close this issue since there hasn't been any update in a long time. If this issue still persists let us know and perhaps we can re-open.

[340rahul]

We're still facing this issue. Is there a workaround?