-
Notifications
You must be signed in to change notification settings - Fork 986
New issue
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
[#21578] Keycard - Factory reset a Keycard #21914
[#21578] Keycard - Factory reset a Keycard #21914
Conversation
Jenkins BuildsClick to see older builds (16)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @flexsurfer for the PR. Looks good to me.
88% of end-end tests have passed
Failed tests (1)Click to expandClass TestWalletMultipleDevice:
Passed tests (7)Click to expandClass TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestWalletOneDevice:
Class TestWalletMultipleDevice:
Class TestCommunityMultipleDeviceMerged:
Class TestCommunityOneDeviceMerged:
|
150aa98
to
9ef178b
Compare
hey @pavloburykh lets pause this PR for now, i'll be back soon with updates, thank you |
thank you @ilmotta all point are valid, I rushed this pull request little bit, it needs more work, also about description you are right i'll change it |
This comment was marked as resolved.
This comment was marked as resolved.
i've implemented only |
this is by design, cc @xAlisher |
@xAlisher can we change this in design? it will simplify development, for user there will be no difference, on try again we just move it to screen there he have all the instructions and can try again |
it's because i implemented different flow, i don't check if keycard is for current profile, i'll add this condition |
|
|
@pavloburykh i checked , card is NOT reseted, not empty error screen is shown, so there is nothing to fix it seems, ready for testing |
100% of end-end tests have passed
Passed tests (8)Click to expandClass TestWalletOneDevice:
Class TestWalletMultipleDevice:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestCommunityMultipleDeviceMerged:
Class TestCommunityOneDeviceMerged:
|
@flexsurfer my bad. I have rechecked and see that it is not reset indeed. |
9ef178b
to
e24261c
Compare
@pavloburykh added 'It's a different keycard` screen |
hey @pavloburykh , after discussing with @xAlisher |
Thank you @flexsurfer! Got a question: according to the new design, after successful keycard reset user is redirected to the Keycard home screen with no Keycard linked https://www.figma.com/design/YGm3igIOAcwMqUVJWCJ6f1/Keycard?node-id=5595-70886&t=hAbB2p3cLP39ZmIX-0 But what if I have reseted the keycard with another profile on it and I still have another keycard linked to current profile? Shouldn't we redirect to the Keycard screen showing this linked keycard? This screen has been removed for some reason. |
hey @pavloburykh sorry for confusion, @xAlisher is working on this and this is a separate issue not related to this PR |
88% of end-end tests have passed
Failed tests (1)Click to expandClass TestCommunityMultipleDeviceMerged:
Passed tests (7)Click to expandClass TestWalletMultipleDevice:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestCommunityOneDeviceMerged:
Class TestWalletOneDevice:
|
Thanks @flexsurfer couple of questions and issues:
What does |
ISSUE 8 Scanning different key card (which is not empty) during Create Profile flow results in stuck on Preparing screen or overwriting keys on this keycardSteps:
Actual result:
Expected result: It's a different key card screen should be shown. Or at least, until this screen is implemented for this flow, we should show Keycard not empty screen. |
@ilmotta some updates on this PR: Following discussions between @flexsurfer and @xAlisher, it was decided to completely remove the separate Keycard reset flow for cases where the Keycard contains the current Profile keys (@flexsurfer can expand on this if needed). From now on, the reset flow will be unified, regardless of whether the Keycard holds current Profile keys or Unknown/Other keys. You can find the updated flow here. Therefore, the following issues are not valid anymore:
Issues which are valid but should be logged/discussed separately:
IMPORTANT: as a part of recent changes, Alisher has updated Keycard home screen BUT current PR does not reflect these changes and according to @flexsurfer they will be implemented in a separate PR. Current PR uses the old screen. |
Thanks @pavloburykh for the detailed heads up 💯
The new text does improve things and it seems to be sufficient for now. As long as we are being upfront and straightforward about the actions that will take place after reset, I think the current UX & copy is sufficient. Over time we will be able to get good feedback from users, and maybe they will have something to say about this part of the flow.
Sure, this one I mentioned originally to @flexsurfer that it is unrelated to this PR. Can be tracked as a separate GH issue 👍🏼 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving since I don't have anything else to add to the PR code-wise, code LGTM.
{:title (i18n/label :t/keycard-reset-success) | ||
:description :text | ||
:description-text (i18n/label :t/keycard-empty-ready)}] | ||
[rn/view {:style {:flex 1}}] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Quick one, what is this rn/view
for? It doesn't have any content or size, that's why I'm asking. File src/status_im/contexts/keycard/different_card/view.cljs
also has this same empty rn/view
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@flexsurfer probably my comment got lost in the myriad of comments in the PR, but could you elaborate on my question above?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh sorry @ilmotta that true, I missed your comment, this view just pushes next view to the bottom
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah okay it's really necessary. Thanks for the explanation!
…nstead of 'This is not a keycard` screen
787916c
to
5ba2af9
Compare
thank you @pavloburykh |
@flexsurfer thanks for the PR. Ready for merge now. |
fixes #21578