allow migration to Keycard keeping the db#12306
Conversation
Jenkins BuildsClick to see older builds (25)
|
| [quo/button {:type :secondary | ||
| :on-press #(re-frame/dispatch [::multiaccounts.key-storage/skip-password-pressed])} | ||
| (i18n/label :t/skip)]]] | ||
| [react/view {:height 1 :background-color colors/gray-lighter}] |
There was a problem hiding this comment.
is this quo/separator ?
87% of end-end tests have passedFailed tests (9)Click to expand
Passed tests (62)Click to expand |
89% of end-end tests have passedFailed tests (1)Click to expand
Passed tests (8)Click to expand
|
|
failed test is because the reset database checkbox is not checked anymore automatically when migrating (by default, we want to keep the db). |
|
@bitgamma thank you! Works great. ISSUE 1: account restored from seed phrase (or private key) remains after moving to keycard storageCurrently, if you create multiaccount with keycard, there is no option to add account in wallet using seed phrase or private key.
Expected result: OS: IOS, Android ISSUE 2: 'Lock app with fingerprint (Face ID)' remains enabled after moving to keycard storageIMO better to reset it and ask user to enable it again, as currently it crashes app on IOS and not working until app reopening (religion) on Android Steps:
Expected result:
|
|
@churik thanks for catching this! should be fixed now. Seed and private keys subaccounts are removed, while watch and derived paths are kept. |
|
@bitgamma previous issues are fixed, thank you! ISSUE 3: "back up seed phrase" is shown if migrate restored multiaccount to keycardSteps:
Expected result: Actual result: OS: IOS, Android |
|
@churik fixed now, thanks! |
|
All fixed.
|
Signed-off-by: Michele Balistreri <michele@bitgamma.com>


Fixes #11777.
Fixes #11659.