We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
addNewAccount
This is part of the effort to consolidate keyring interactions between extension and mobile. Originally proposed here.
In the mobile client, the core KeyringController is patched to not switch accounts after creating a new one.
We should remove the account switch from the core KeyringController implementation, leaving this responsibility to clients.
The text was updated successfully, but these errors were encountered:
mikesposito
Successfully merging a pull request may close this issue.
This is part of the effort to consolidate keyring interactions between extension and mobile.
Originally proposed here.
Context
In the mobile client, the core KeyringController is patched to not switch accounts after creating a new one.
Solution
We should remove the account switch from the core KeyringController implementation, leaving this responsibility to clients.
The text was updated successfully, but these errors were encountered: