-
Notifications
You must be signed in to change notification settings - Fork 990
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
add navigate biometric screen after sign-in by syncing #17627
Conversation
0b4cbb1
to
21452f2
Compare
Jenkins BuildsClick to see older builds (109)
|
45682ce
to
019c6e5
Compare
2efab21
to
2260b1f
Compare
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.
After enabling biometric authentication in the sync flow, the 'Unlock with Biometric' screen is not appearing upon subsequent app openings.
Should we create a separate issue to address the addition of the 'Preparing status for you' screen?
@ajayesivan I thought adding the |
@ajayesivan thanks for pointing that out. it works well on android but looks like on ios there is still something to do to make it work on app relaunch. Am working on it |
86977dd
to
f8c7a08
Compare
dbae1fe
to
dada4e4
Compare
@ajayesivan On relaunch biometrics works well now |
@jo-mut the issue is reproducible in the builds with commit dea9b0d These were the latest available builds when I was testing this PR. ![]() I have just tried the latest builds after your recent rebasing and I am not reproducing ISSUE 2 anymore.
@jo-mut is the design team aware about this technical limitations and current solution confirmed with them? Asking because I do not see any updates in Figma. I believe that whenever we need to update the flow due to any technical reason we should bring this to designers as well so they confirm solution from their perspective. Meanwhile, I think that name of the button should be changed. Instead of "Password" we need something which describes the action like Confirm/Proceed/Next etc. |
@pavloburykh I think |
@@ -35,11 +35,30 @@ | |||
{:biometric/authenticate {:on-success #(rf/dispatch [:onboarding-2/biometrics-done]) | |||
:on-fail #(rf/dispatch [:onboarding-2/biometrics-fail %])}}) | |||
|
|||
(rf/defn authenticate-enable-biometrics |
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.
@jo-mut - I think there is a slightly better approach to take here. I will make a suggested commit and you can let me know what you think 👍
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.
please see 1392a4e - I have this code pushed on branch jc/standard-auth-refactor
The problem here is that the standard auth code only exposes a slide button, so you had to make these adjustments for it to work with the quo/button.
The better approach imo is to add another component in standard-auth "module" - which uses quo/button component under the hood, we can then encapsulate all of this authorization logic in there 👍
I think we will need for many other screens anyway so it would be good to have this added in 👍
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.
I made a slight adjustment - 1ad8626 (also updated requires in wallet screens 👍 )
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.
@J-Son89 I have looked at your branch. I agree with your suggestions. thanks
Design input required @status-im/design-team . Link to the discussion |
13bbf97
to
c3027ed
Compare
49% of end-end tests have passed
Failed tests (21)Click to expandClass TestCommunityMultipleDeviceMergedTwo:
Class TestCommunityOneDeviceMerged:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestCommunityMultipleDeviceMerged:
Expected to fail tests (2)Click to expandClass TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestGroupChatMultipleDeviceMergedNewUI:
Passed tests (22)Click to expandClass TestActivityMultipleDevicePRTwo:
Class TestCommunityOneDeviceMerged:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestActivityCenterContactRequestMultipleDevicePR:
Class TestActivityMultipleDevicePR:
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
Class TestCommunityMultipleDeviceMergedTwo:
|
@J-Son89 could you take a look at this pr once again. I included your suggestions here #17627 (comment). Am just wondering so e2e test have a pass rate that is so low |
We are experiencing global failing of e2e right now. Currently investigating the reason. |
44% of end-end tests have passed
Failed tests (22)Click to expandClass TestCommunityMultipleDeviceMergedTwo:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestActivityMultipleDevicePR:
Class TestActivityMultipleDevicePRTwo:
Class TestCommunityOneDeviceMerged:
Class TestCommunityMultipleDeviceMerged:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Expected to fail tests (3)Click to expandClass TestGroupChatMultipleDeviceMergedNewUI:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Passed tests (20)Click to expandClass TestCommunityMultipleDeviceMergedTwo:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestActivityCenterContactRequestMultipleDevicePR:
Class TestCommunityOneDeviceMerged:
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
|
18% of end-end tests have passed
Failed tests (18)Click to expandClass TestActivityMultipleDevicePR:
Class TestCommunityOneDeviceMerged:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestCommunityMultipleDeviceMerged:
Class TestActivityMultipleDevicePRTwo:
Passed tests (4)Click to expandClass TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestCommunityMultipleDeviceMergedTwo:
|
c3027ed
to
570a43f
Compare
73% of end-end tests have passed
Failed tests (9)Click to expandClass TestCommunityOneDeviceMerged:
Class TestActivityCenterContactRequestMultipleDevicePR:
Class TestGroupChatMultipleDeviceMergedNewUI:
Expected to fail tests (3)Click to expandClass TestOneToOneChatMultipleSharedDevicesNewUiTwo:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestGroupChatMultipleDeviceMergedNewUI:
Passed tests (33)Click to expandClass TestActivityMultipleDevicePRTwo:
Class TestCommunityOneDeviceMerged:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestCommunityMultipleDeviceMerged:
Class TestActivityMultipleDevicePR:
Class TestActivityCenterContactRequestMultipleDevicePR:
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
|
@J-Son89 @ajayesivan may I ask you to confirm that your review comments were addressed? |
@J-Son89 thank you |
@jo-mut please, cherry-pick your commit to release branch, thanks! |
570a43f
to
54a0e6c
Compare
54a0e6c
to
3e4ef18
Compare
fixes #15643
Summary
This pr adds
enable biometrics screen
in the sign-in flow.Review notes
It does not include the
preparing status for you
screen in the following figma link belowhttps://www.figma.com/file/o4qG1bnFyuyFOvHQVGgeFY/Onboarding-for-Mobile?type=design&node-id=3515-358293&mode=design&t=shfNKJEPbKyMj2cx-4
Platforms
Steps to test
status: ready