-
Notifications
You must be signed in to change notification settings - Fork 985
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
fix: unresponsive add watched address screen when entering a multi-chain address #19185
Conversation
Jenkins BuildsClick to see older builds (8)
|
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.
Nice 👌
81% of end-end tests have passed
Failed tests (8)Click to expandClass TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestActivityCenterContactRequestMultipleDevicePR:
Expected to fail tests (1)Click to expandClass TestCommunityOneDeviceMerged:
Passed tests (39)Click to expandClass TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestActivityMultipleDevicePR:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestCommunityOneDeviceMerged:
Class TestActivityCenterContactRequestMultipleDevicePR:
Class TestActivityMultipleDevicePRTwo:
Class TestCommunityMultipleDeviceMerged:
Class TestDeepLinksOneDevice:
|
@@ -22,6 +23,10 @@ | |||
(or (validation/eth-address? user-input) | |||
(validation/ens-name? user-input))) (i18n/label :t/invalid-address))) | |||
|
|||
(defn- extract-address | |||
[scanned-text] | |||
(first (re-seq constants/regx-address-contains scanned-text))) |
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.
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.
Thanks @ulisesmac, updated the function :)
Additionally, I'm wondering what happens when it's not found? is that case properly handled?
That should not happen as we are calling extract-address
with :wallet/watch-address-validated-address
sub value, and it always returns a valid address. If there's no valid address the button is disabled and extract-address
is never called.
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.
Ok 👍 thanks for the explanation
94% of end-end tests have passed
Failed tests (2)Click to expandClass TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestCommunityMultipleDeviceMerged:
Expected to fail tests (1)Click to expandClass TestCommunityOneDeviceMerged:
Passed tests (45)Click to expandClass TestDeepLinksOneDevice:
Class TestActivityCenterContactRequestMultipleDevicePR:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestCommunityMultipleDeviceMerged:
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
Class TestCommunityOneDeviceMerged:
Class TestActivityMultipleDevicePRTwo:
Class TestActivityMultipleDevicePR:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
|
fee8074
to
7c10fda
Compare
7c10fda
to
7194682
Compare
Hi @briansztamfater ! |
7194682
to
211901a
Compare
fixes #18950
Summary
This PR aims to fix unresponsive add watched address screen when entering a multi-chain address. The approach I took is to extract the plain address from the multi-chain address so status-go endpoint doesn't return an error and the flow continues as expected. Either way address is watched for all the available chains.
Platforms
Areas that maybe impacted
Functional
Steps to test
+
to add new watch addresseth:opt:arb1:0x9bf27d0c9aba562dc33bc4b60c233a6609ce2987
)Confirm
to navigate to the next screenAdd watched address
status: ready