Michele Esposito

@metamaskbot update-policies

@metamaskbot update-policies

@metamaskbot update-policies

As suggested by @legobeat, I included the `signature-controller` bump to `^14.0.1` in this PR and changed title and description accordingly

The import account flow still uses the old return that used to include the mem state: (`app/util/address/index.js`) The function `importAccountFromPrivateKey`: ```typescript const { importedAccountAddress } = await KeyringController.importAccountWithStrategy('privateKey', [pkey]); ```...

Nit (here or another PR): we could make [this function](https://github.com/MetaMask/metamask-mobile/blob/58c377ad4690a448d17bbf315f1a1882b6a5ab89/app/util/importAdditionalAccounts.js#L32-L33) to recreate primary accounts with balance "without update" better with `withKeyring`

> Ledger Transaction Issue: Encountered an inability to transact using Ledger across all devices. @plasmacorral could you confirm that the Ledger device connection (to add an account) was successful, thus...

@SocketSecurity ignore npm/@metamask/[email protected] This is our package

I'm unable to test this locally, but [135e572](https://github.com/MetaMask/metamask-mobile/pull/9570/commits/135e572569c27ae5393639959bb43036c894884c) should fix the issue with Ledger (1) and [c5bd3db](https://github.com/MetaMask/metamask-mobile/pull/9570/commits/c5bd3db4ad2f12e03b21f1367c99ca1967b8b5a8) should fix the error when importing an account (2) > QR Account Labels...

> QR accounts are being duplicated when closing the app and reopening Hi @vivek-consensys, looking at your screen recording it looks like QR accounts are not being duplicated during login...