This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
Intro screen requiring new account upon every restart if all current accounts are in a Vault #4894
Assignees
Labels
F2-bug 🐞
The client fails to follow expected behavior.
Comments
|
Just tested, can reproduce. |
|
Yes, would be an issue & oversight. Since the UI pops up the account creation when no accounts are found (and it doesn't have any access to vault accounts until the vault has been opened). As a work-around, keep a single account out of the vaults, will need to see what we can do logic wise, maybe "no accounts" & "no vaults" as a determination instead of just "no accounts". |
ngotchac
added a commit
that referenced
this issue
Mar 15, 2017
gavofyork
pushed a commit
that referenced
this issue
Mar 15, 2017
jacogr
pushed a commit
that referenced
this issue
Mar 22, 2017
arkpar
pushed a commit
that referenced
this issue
Mar 22, 2017
* [ci skip] js-precompiled 20170314-121823 * Attach hardware wallets already in addressbook (#4912) * Attach hardware wallets already in addressbook * Only set values changed * Add Vaults logic to First Run (#4894) (#4914) * Add ability to configure Secure API (for #4885) (#4922) * Add z-index to small modals as well (#4923) * eth_sign where account === undefined (#4964) * Update for case where account === undefined * Update tests to not mask account === undefined * default account = {} where undefined (thanks @tomusdrw) * Fix Password Dialog forms style issue (#4968)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Upon upgrading to 1.6.2, after putting accounts into vault, every time I load up Parity I need to create a new account just to get past the parity intro screen.
The text was updated successfully, but these errors were encountered: