[Bug]: calling wallet_requestPermissions providing an address is ignored

[shanejonas]

Describe the bug

1. wallet_requestPermission is not respecting the caveats in the permissions approval screen that pops up. the approval UI screen should show the the addresses passed in pre selected the UI.

Steps to reproduce

1. requestPermissions with an account that is not currently selected:

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

or

         await window.ethereum.request({
          method: 'wallet_requestPermissions',
          params: [
            {
              eth_accounts: {
                "caveats": [
                  {
                    "type": "restrictReturnedAccounts",
                    "value": [
                      "0xf39fd6e51aad88f6f4ce6ab8827279cfffb92266"
                     ]
                  }
                ]
              },
            },
          ],
        })

2. see that it is not pre selected in the approval UI

Error messages or log output

No response

Version

10.34.0

Build type

None

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

No response

[vandan]

You have to be on a different account to reproduce this issue.

[vandan]

May relate to this MIP: MetaMask/metamask-improvement-proposals#24

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions.

[github-actions]

This issue was closed because there has been no follow up activity in the last 45 days. If you feel this was closed in error, please reopen and provide evidence on the latest release of the extension. Thank you for your contributions.